From majordomo-workers-owner@greatcircle.com Mon Aug 19 20:39:47 2002 Received: from daniel.liston.nu (58-25.siocpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6C8751960F1; Mon, 19 Aug 2002 20:39:43 -0700 (PDT) Received: from sonny.org (daniel.sonny.org [24.116.58.25]) by daniel.liston.nu (8.11.6/8.11.6) with ESMTP id g7K3cqn18184; Mon, 19 Aug 2002 22:38:53 -0500 Message-ID: <3D61B9CC.3D6A9F4C@sonny.org> Date: Mon, 19 Aug 2002 22:38:52 -0500 From: Daniel Liston X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-users , Majordomo-workers@greatcircle.com Subject: config-test.0 patch Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200208/1 X-Sequence-Number: 4 I just wanted to add my 2 cents worth on the config-test.0 patch. I like it, it is very simple, but I disagree with the " - should be 777" portion of the very first change. If you are running sendmail 8.9.3 or newer, the 777 permission on the lists directory will prevent you from distributing mail to the aliases with :include: on the RightHandSide. 755 is about as loose as you dare to go. If you are security conscious, 751 would be even better. Dan Liston From majordomo-workers-owner@greatcircle.com Sat Aug 31 17:44:44 2002 Received: from daniel.liston.nu (58-25.siocpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8D45B195AAB for ; Sat, 31 Aug 2002 17:44:41 -0700 (PDT) Received: from sonny.org (gw2.liston.nu [192.168.1.2]) by daniel.liston.nu (8.11.6/8.11.6) with ESMTP id g810hl408388 for ; Sat, 31 Aug 2002 19:43:47 -0500 Message-ID: <3D7162C3.8040707@sonny.org> Date: Sat, 31 Aug 2002 19:43:47 -0500 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2) Gecko/20020618 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-workers@greatcircle.com Subject: fronters/footers idea Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200208/2 X-Sequence-Number: 5 I am not sure if anyone still uses this list :) but I have a "what if" idea for dealing with MIME content messages when a list utilizes fronters or footers. I know we want to convince users to stick to plain text, but as someone mentioned on the -users list, MIME will not be going away, and we need to deal with it. Does anyone think it is worth the effort during the body/header parsing to add this kind of logic? If header_content_type m/multipart/i boundary = split('=', whatever goes here) fi inserting a fronter would become if boundary --$boundary Content-Type: text/plain fi $fronter Inserting/appending a footer would become if boundary $_ =~ s/--$boundary--/--$boundary/ Content-Type: text/plain fi $footer if boundary --$boundary-- fi In other words, to quote from someone on the mailman list, if a message has MIME parts and the header/footer is going to be added, the message should be transformed into a mulitpart/mixed with the header and footer added as text/plain parts. Is my logic above over simplified? Dan Liston From majordomo-workers-owner@greatcircle.com Sat Aug 31 21:36:09 2002 Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8A8E3195AAC for ; Sat, 31 Aug 2002 21:36:07 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.11.2/8.11.1) id g814ZBF16349; Sat, 31 Aug 2002 23:35:11 -0500 To: Daniel Liston Cc: majordomo-workers@greatcircle.com Subject: Re: fronters/footers idea References: <3D7162C3.8040707@sonny.org> From: Jason L Tibbitts III Date: 31 Aug 2002 23:35:10 -0500 In-Reply-To: Daniel Liston's message of "Sat, 31 Aug 2002 19:43:47 -0500" Message-ID: Lines: 10 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200208/3 X-Sequence-Number: 6 >>>>> "DL" == Daniel Liston writes: DL> Does anyone think it is worth the effort during the body/header DL> parsing to add this kind of logic? Majordomo2 will attach fronters and footers as MIME parts when appropriate, but we do avoid complicating the MIME structure by adding additional nesting where it's not already present. - J<