On 18 Mar 00 at 22:53, Dale Mentzer wrote: > I would have switched to digest quite some time ago, if it was > available in mime format. Pegasus for DOS handles each message > separately in mime format digests (like SurvPC) which makes > reading/replying much easier. Is this available with Arachne > digest? I usually prefer the MIME digest format when possible too, for the same reasons you do, but also since it means less wasted disk space for messages saved. But if you can't have it, you can create your own with Digester :) Works in DOS even if focus on WinPmail in the snippet that follows below. My comments follow after. Snipped from: Guide to Pegasus Mail Addons List URL: ftp://ftp.demon.co.uk/pub/ibmpc/dos/apps/pmail/pmail-addons.txt # begin copy Name of Program: DIGESTER: Pegasus Listserv Digest Processor Location/Filename: <URL :ftp://risc.ua.edu/pegasus/misc/digester.zip> <URL: http://www.users.globalnet.co.uk/~stephenk/files/digester.zip> Date/Version: Jun 97 ver 2.30 Author/email contact: Stephen Knight <[EMAIL PROTECTED]> Status: Freeware Documentation: Basic instructions Features: DIGESTER is a small filter program for WinPMail to convert list server digests that don't support MIME Digests directly into multi-part MIMEDigest messages. Comments: Written in Quick Basic, source code available on request. Known to work with PMAIL, NOVELL, and VEGAN-L lists. Others separated by a line of dashes should work too. About 40k in size. # end copy I use the above Digester all the time. I use WinPmail though, which trigger Digester via a filtering rule. Thus when incoming From header says: "arachne-owner" - it copies and converts the incoming message to MIME digest format. Can be run from DOS command line with: DIGESTER <output path> <input filename> Works just fine with the Arachne digest.. With some Mailing List Managers (MLM) the message separator line used in the digest format will not be recognized by Digester though (standard listserv and majordomo usually works fine). If so, I just use a search/replace routine to replace every instance of the "offending" message separator in the incoming digest with one that works. (like the one from the Arachne digest ) When creating the mime digest, it also inserts two mailto links on the two first lines of each message body, in the following format (this is from the message I reply to now :) Reply to Sender: mailto:[EMAIL PROTECTED] Reply to List: mailto:[EMAIL PROTECTED] In another message you wrote: > Pegasus for DOS does this also with mime format digests. I have to > remember to manually put the list address in the message before > sending. Therefor the above mentioned feature of Digester is very nice. But when this is said, i don't think what you mention is a feature of Pegasus, more a result and requirement following from the message format, where each message inside the MIME digest is expected to been seen as/ treated as individual messages, separated by a mime boundary line. It would no longer be if the client used the headers from the container (mother) message when forming a reply. If you want the blame someone <g>, blame the MLM who picked the headers to be included with each message in the digest. ;) (but I believe this format is also set in some RFC, not sure though ) As to what have been said here recently about Reply-to Vs From headers, I believe the "order of things" where set out in some RFC, Reply-to first, From only if Reply-to is empty or missing. Thus this should not be left as matter of personal preference for the author. But client may of course prompt the user and ask: use this or that or all? But else, reply-to first, then from. If memory serves... All the best, Bjorn
