From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11541 Path: main.gmane.org!not-for-mail From: Justin Sheehy Newsgroups: gmane.emacs.gnus.general Subject: Re: compatibility of nnml and MH Date: 10 Jul 1997 08:42:30 -0400 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035151234 30954 80.91.224.250 (20 Oct 2002 22:00:34 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:00:34 +0000 (UTC) Return-Path: Original-Received: from sandy.calag.com (root@sandy [206.190.83.128]) by altair.xemacs.org (8.8.6/8.8.6) with ESMTP id GAA14448 for ; Thu, 10 Jul 1997 06:55:46 -0700 Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by sandy.calag.com (8.8.6/8.8.6) with ESMTP id GAA28997 for ; Thu, 10 Jul 1997 06:53:00 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id IAA05577 for ; Thu, 10 Jul 1997 08:52:38 -0500 (CDT) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Thu, 10 Jul 1997 14:42:38 +0200 Original-Received: (qmail 16395 invoked by uid 504); 10 Jul 1997 12:42:36 -0000 Original-Received: (qmail 16392 invoked from network); 10 Jul 1997 12:42:34 -0000 Original-Received: from linus.mitre.org (129.83.10.1) by claymore.vcinet.com with SMTP; 10 Jul 1997 12:42:33 -0000 Original-Received: from geeky.mitre.org (geeky.mitre.org [129.83.10.221]) by linus.mitre.org (8.8.6/8.8.6) with ESMTP id IAA05886 for ; Thu, 10 Jul 1997 08:42:32 -0400 (EDT) Original-Received: (from justin@localhost) by geeky.mitre.org (8.8.5/8.8.5) id IAA19359; Thu, 10 Jul 1997 08:42:30 -0400 (EDT) Original-To: ding@gnus.org In-Reply-To: Jason R Mastaler's message of "09 Jul 1997 23:37:39 -0600" X-Mailer: Gnus v5.4.62/Emacs 19.34 Original-Lines: 47 Original-Xref: altair.xemacs.org dgnus-list:1931 Xref: main.gmane.org gmane.emacs.gnus.general:11541 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11541 Jason R Mastaler writes: > I'm not interested in reading existing nnml groups with MH or MH > front-end Too bad. :-) That's the easy part. > but I am interested in being able to manipulate saved articles from > those nnml groups at a later date with MH and not run into problems. If you manipulate nnml group messages with anything but Gnus (such as mh), it will probably work but will be very likely to cause problems for Gnus when you next try to read said group. If you are not interested in reading them as nnml messages again, then you can treat them as mh messages with impunity. > Also, there seems to be conflicting ideas about the compatibility > of nnml with other formats (such as MH). [snip] > This seems to imply that nnml is somewhat compatable with MH since > nnmh (which is MH compliant) is "just like `nnml', except that is > doesn't generate NOV databases and it doesn't keep an active file". > Is the existance of the NOV databases and active file enough to > introduce these incompatibilities? It really doesn't seem like it > could, so is there something else I've missed? It is. nnml and nnmh both use exactly the same format for storing the actual messages, which is the mh spool format. nnml also stores additional, Gnus-specific data. Altering the messages from outside of Gnus is likely to make the nnml group misbehave. So, you can read either one with mh. If you are planning on switching back and forth between Gnus and mh for _altering_ the messages, then stick with nnmh. -- Justin Sheehy In a cloud bones of steel.