From majordomo-workers-owner Fri Jul 2 07:33:16 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA27179; Fri, 2 Jul 1999 07:30:10 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA27172 for ; Fri, 2 Jul 1999 07:30:05 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id JAA18791; Fri, 2 Jul 1999 09:35:29 -0500 To: Dr ZP HAN Cc: majordomo-workers@greatcircle.com Subject: Re: Suggestion for mj2 References: From: Jason L Tibbitts III Date: 02 Jul 1999 09:35:29 -0500 In-Reply-To: Dr ZP HAN's message of "Fri, 2 Jul 1999 13:11:11 +0100 (BST)" Message-ID: Lines: 11 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "ZH" == ZP HAN writes: ZH> It'd be nice if the list owner could decide whether non-subscribers' ZH> messages are sent back to the sender or to the list owner. This has been implemented since the beginning. You can even customize the message or send different messages for different kinds of bounces. If you're using Mj2 currently, I'd be happy to give you some help configuring this. - J< From majordomo-workers-owner Sat Jul 3 13:39:36 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA16140; Sat, 3 Jul 1999 13:28:41 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id NAA16118 for majordomo-workers@greatcircle.com; Sat, 3 Jul 1999 13:28:35 -0700 (PDT) Received: from oxmail.ox.ac.uk (oxmail3.ox.ac.uk [163.1.2.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA25822 for ; Fri, 2 Jul 1999 05:09:49 -0700 (PDT) Received: from ermine.ox.ac.uk ([163.1.2.13]) by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1) id 11029v-0007bU-00; Fri, 2 Jul 1999 13:11:11 +0100 Received: from ermine.ox.ac.uk ([163.1.2.13] ident=zph) by ermine.ox.ac.uk with esmtp (Exim 2.12 #1) id 11029v-00081A-00; Fri, 2 Jul 1999 13:11:11 +0100 Date: Fri, 2 Jul 1999 13:11:11 +0100 (BST) From: Dr ZP HAN To: majordomo-workers@greatcircle.com cc: tibbs@math.uh.edu Subject: Suggestion for mj2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi, mj2 developers: It'd be nice if the list owner could decide whether non-subscribers' messages are sent back to the sender or to the list owner. -- Zong-Pei (UNIX SYS Admin) From majordomo-workers-owner Sat Jul 3 13:49:34 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA15838; Sat, 3 Jul 1999 13:23:49 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA15828 for ; Sat, 3 Jul 1999 13:23:38 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id PAA05943; Sat, 3 Jul 1999 15:28:26 -0500 To: Ben Smithurst Cc: majordomo-workers@greatcircle.com Subject: Re: majordomo/exim/spam issue References: <19990630144442.A3648@rainbow5.scientia.demon.co.uk> <19990703180147.A21904@rainbow5.scientia.demon.co.uk> From: Jason L Tibbitts III Date: 03 Jul 1999 15:28:26 -0500 In-Reply-To: Ben Smithurst's message of "Sat, 3 Jul 1999 18:01:47 +0100" Message-ID: Lines: 25 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [Note to Majordomo-Workers: this is moving from the Exim mailing list.] >>>>> "BS" == Ben Smithurst writes: BS> Well, since the separator is director specific in Exim, you could BS> either just ask them what separator they want to use, and insert the BS> appropriate line in the Exim config file. Well, basically I was just asking why we don't just use '+' and not bother the user about it. I was originally under the impression that the separator was either chosen once or even compiled in so I added the configuration question, but if we get to pick, it would be simpler just to pick one thing and use it. BS> p.s., for lazy people like me, it would be nice if Mj2 installation BS> could add the director to Exim's config automatically, though I'm not BS> sure how easy that would be. The basic idea is that Majordomo only messes with files that it has explicit control over. Actually mucking with peoples' MTA config files seems to me to be extremely dangerous because of the variety of different ways folks can configure things. However, if you want to have a go I'll be more than happy to include what you come up with. - J< From majordomo-workers-owner Sat Jul 3 15:49:08 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA17742; Sat, 3 Jul 1999 15:42:58 -0700 (PDT) Received: from miles.greatcircle.com (miles.greatcircle.com [198.102.244.45]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA17735 for ; Sat, 3 Jul 1999 15:42:50 -0700 (PDT) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by miles.greatcircle.com (8.8.5/8.8.5) with ESMTP id PAA29022 for ; Sat, 3 Jul 1999 15:45:05 -0700 (PDT) Received: from rainbow5.scientia.demon.co.uk ([192.168.1.2] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.02 #1) id 110WW7-0009gq-00; Sat, 03 Jul 1999 21:36:07 +0100 (envelope-from ben@rainbow5.scientia.demon.co.uk) Received: from rainbow5.scientia.demon.co.uk (ident=ben) by rainbow5.scientia.demon.co.uk with local (Exim 3.02 #1) id 110WW8-0005zI-00; Sat, 03 Jul 1999 21:36:08 +0100 (envelope-from ben@rainbow5.scientia.demon.co.uk) Date: Sat, 3 Jul 1999 21:36:08 +0100 From: Ben Smithurst To: Jason L Tibbitts III Cc: majordomo-workers@greatcircle.com Subject: Re: majordomo/exim/spam issue Message-ID: <19990703213608.A22984@rainbow5.scientia.demon.co.uk> References: <19990630144442.A3648@rainbow5.scientia.demon.co.uk> <19990703180147.A21904@rainbow5.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Jason L Tibbitts III wrote: > [...] if we get to pick, it would be simpler just to pick one thing > and use it. > > [...] Actually mucking with peoples' MTA config files seems to me to > be extremely dangerous because of the variety of different ways folks > can configure things. [...] Agreed on both counts, after thinking about making code to edit Exim's config file. It just doesn't seem worth it, for a one off edit like this. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk From majordomo-workers-owner Wed Jul 7 00:03:56 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id XAA05545; Tue, 6 Jul 1999 23:47:41 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id XAA05510 for majordomo-workers@greatcircle.com; Tue, 6 Jul 1999 23:47:32 -0700 (PDT) Received: from mail.dnt.ro (ns.dnt.ro [193.226.100.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA18203; Mon, 5 Jul 1999 15:29:09 -0700 (PDT) Received: from zero.dnt.ro (zero.dnt.ro [193.226.100.41]) by mail.dnt.ro (8.9.3/8.9.3) with ESMTP id BAA05926; Tue, 6 Jul 1999 01:30:59 +0300 Date: Tue, 6 Jul 1999 01:36:10 +0300 (EEST) From: Stefanita Vilcu To: majordomo-workers@greatcircle.com cc: majordomo-users@greatcircle.com Subject: majordomo 2 does not restrict posts? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk hello, I have installed the latest version of majordomo on a RedHat 6.0 i386 linux. It seems to work ok but it is not restricting the posts only to the list members. On the moderated lists it is ok. I use the defaut configuration for an unmoderated, open+confirm list access. I think I am wrong, but where? TIA -vsv the config file follows: # access_password_override # (yes) [bool] # This controls whether or not the restrictions given in access_rules # can always be overridden with a password. If this is set to no, then # a supplied password is just another variable that can be used in the # access table. # # WARNING: use this variable with care. It is possible to lock yourself # out of your lists if you do not grant some password access. configset shop access_password_override = 1 # access_rules # (empty) [access_rules] # # A table containing access rules. This is a very powerful and # unfortunately somewhat complicated mechanism for precisely restricting # access to Majordomo functions which I will document later. # configset shop access_rules << ENDAAB ENDAAB # ack_attach_original # (fail ...) [enum_array] # This controls under what circumstances the original message will be # attached (as a MIME attachment) to acknowlegements sent out to inform # the user of delivery progress (as set by the user''s ack setting and # the value of the 'ack_denials_always' variable). # # Each element of this array must be one of the following: # # fail - acks for failed messages will include the original message # stall - acks for stalls (confirmations or consultations) will # include the original message. # all - acks sent for any reason will include the original message. configset shop ack_attach_original << ENDAAC fail stall ENDAAC # ack_denials_always # (yes) [bool] # If this is on, users whose posts are denied will always be informed of # the denial. Otherwise they will be informed based on their flag # settings: if they have either the 'ackall' or 'ackimportant' flag set # then they will receive notice of the denial, else they will not # recieve any type of notice. configset shop ack_denials_always = 1 # admin_body # (empty) [taboo_body] # If any line of the body matches one of these regexps, then the message # will be bounced for review. XXX Ugh. configset shop admin_body << ENDAAD ENDAAD # admin_headers # (empty) [taboo_headers] # If any of the headers matches one of these regexps, then the message # will be bounced for review. XXX Ugh. configset shop admin_headers << ENDAAE ENDAAE # administrivia # (yes) [bool] # Look for administrative requests (e.g. subscribe/unsubscribe) and # forward them to the list maintainer instead of the list. configset shop administrivia = 1 # advertise # (empty) [regexp_array] # If the requestor name matches one of these regexps, then the list will # not be listed in the output of a lists command. Noadvertise overrides # advertise. configset shop advertise << ENDAAF ENDAAF # allowed_classes # (each ...) [string_array] # A list of the classes that a user is allowed to put themselves into. # If a less specific class like 'digest' is given, users are allowed # to put themselves into any of the more specific classes. configset shop allowed_classes << ENDAAG each digest nomail ENDAAG # allowed_flags # (ACHPRS) [string] # A string containing the flags that users are allowed to adjust. You # need only include the uppercase flags here: # # A - ack # C - eliminatecc # H - hide # P - prefix # R - replyto # S - selfcopy # # If this is completely empty, users cannot adjust any of their flags. # The list owner can of course do so. configset shop allowed_flags = ACHPRS # archive_dir # () [directory] # The directory where the mailing list archive is kept. # # If this is not set, Majordomo will look for a directory named "archive" in # the public directory of the filespace. If it exists, archives will be # placed there. If not, archives will not be generated and digests will not # function. configset shop archive_dir = /home/majordomo/archive/shop # archive_size # (unlimited) [string] # A string decribing the maximum size of a single archive file. When a # message arrives that would cause an archive file to exceed the size set # here, a new archive file is created with the final number incremented by # one. # # Possible values are an integer followed by one of k, or m for # kilobytes or messages. The value 'unlimited' is also permitted, in # which case the archives will not have the following period and two # digits appended. # # Note that changing this variable will only change the settings for new # messages; old archives will not be renamed or altered in any way. configset shop archive_size = unlimited # archive_split /yearly,monthly,weekly,daily/ # (monthly) [enum] # A word describing how the archive files should be split. Here are the # possibilities, along with sample names of the archive files: # # yearly - 1999.00 # monthly - 199903.00 # weekly - 20021031.00 # daily - 21121002.00 # # Note that archives will be further split by size; see the archive_size # variable. This gives rise to the two trailing digits, which may not be # present depending on the archive_size setting. # # Also note that changing this variable will only change the settings for new # messages; old archives will not be renamed or altered in any way. configset shop archive_split = monthly # attachment_rules # (empty) [attachment_rules] # # A table containing attachment rules, which describe how various MIME # types are to be treated when they appear in messages sent to the list. # # A rule consists of a MIME type (or regular expression matching a MIME # type) and a list of actions to perform when a message with this type # or containing a part of this type passes through the list. It looks # something like this: # # mime/type | action=argument # # Some MIME types are: # # text/plain, text/html, image/jpeg, video/mpeg # # Possible actions are: # # allow - let the part pass # deny - reject the entire message # discard - remove the part from the message and pass the rest # consult - send the entire message to the list owner for approval # (more are planned) # # allow and consult take an argument; if present, it should be a # content-transfer-encoding. configset shop attachment_rules << ENDAAH ENDAAH # bounce_probe_frequency # (0) [integer] # This variable controls how often bounce probes are sent out. # # The address list is split into 'bounce_probe_frequency' pieces, and a # different piece is probed for each message sent to the list. This lowers # the overall load while still allowing complete probes to be done in a # reasonable amount of time. # # Setting this to zero disables regular bounce probing. Setting this to one # probes every address for every message and may place an extreme load on the # server(s). Note that this variable will be ignored if the MTA is qmail, # because qmail does an equivalent kind of bounce probing itself. configset shop bounce_probe_frequency = # category # () [string] # A string used to categorize the list. Any string can be chosen; the # value is used only in the output of the lists command to group and # sort lists. configset shop category = # comments # (empty) [string_array] # Comment string that will be retained across config file rewrites. configset shop comments << ENDAAI ENDAAI # date_info # (yes) [bool] # Put the last updated date for the info file at the top of the info # file rather than having it appended with an info command. This is # useful if the file is being looked at by some means other than # majordomo (e.g. finger). configset shop date_info = 1 # date_intro # (yes) [bool] # Put the last updated date for the intro file at the top of the intro # file rather than having it appended with an intro command. This is # useful if the file is being looked at by some means other than # majordomo (e.g. finger). configset shop date_intro = 1 # debug # (0) [integer] # When MTA configuration is suggested, this value will be used as the # debug parameter. It is used to generate debugging information for # this list. Higher values cause more debugging information to be # generated. Values of 500 are generally sufficient for bug reporting; # at 1000 a complete SMTP trace is generated which is useful for # debugging MTA problems. # # Note that this only effects the generation of the MTA configuration # information (i.e. suggested aliases) so that configuration information # will have to be updated for this value to have any effect. # # If the MTA configuration is being automatically maintained by # Majordomo, it should be regenerated (using createlist-regen). configset shop debug = 500 # default_class # (each) [string] # When users first subscribe, they will be placed into this class. If # the class given does not exist, they will be placed into the 'each' # class, where they receive each message. configset shop default_class = each # default_flags # (SPR) [string] # A string containing the flags to be given to new subscribers unless they # choose otherwise. Possible flags are: # # A - ackall # a - ackimportant # C - eliminatecc # H - hideall # h - hideaddress # P - prefix # R - replyto # S - selfcopy configset shop default_flags = SPR # default_language # (en) [string] # This sets the default language for the list (or the installation). # This is overridable by the user in several ways. Note that at this # time this is barely implemented. (Only English messages are supported # at the moment.) configset shop default_language = en # delete_headers # (X-Confirm-Reading-To ...) [string_array] # Headers appearing in this list will be removed from the messages # before being passed on to the recipients or placed into the archive. configset shop delete_headers << ENDAAJ X-Confirm-Reading-To X-Ack Sender Return-Receipt-To Flags Priority X-Pmrqc Return-Path Delivered-To ENDAAJ # delivery_rules # (empty) [delivery_rules] # # A table containing delivery rules, which describe how Majordomo will # deliver mail. In the simplest form, you can specify a host to use for # delivery and a batch size. (This duplicates much of the functionality # of bulk_mailer, for those familiar with it.) # # Each delivery destination should begin with a line containing either a # regular expression, or the word ALL. Addreses are compared against # these in order; the first matching destination is chosen. This # enables you to choose which addresses go to which sets of hosts. # # The remaining lines (up until the next blank) should consist of # various parameters which affect delivery. The possible parameters # are: # # numbatches=N # Split the address list up into exactly N batches. # # maxaddrs=N # Split the list into batches of N addresses apiece. # # maxdomains=N # Split the address list into batches of N domains apiece. # # minseparate=N # If a domain appears more than N times in various addresses, they # will all be given a separate batch. # # If neither of the above are specified, the default is numbatches=1, # which duplicates the Majordomo 1.x behavior. # # hosts=(hosta, hostb, hostc) # A list of hostnames that Majordomo will connect to to deliver # batches. If no hosts are given, Majordomo connects to localhost. # # backup=(hostd, hoste, hostf) # A list of backup hosts to use in case one or more of the regular # delivery hosts are down. # # sort # Sort the address list. Many of the batching options depend on # getting the addresses in sorted order and will not work as expected # if the address are unsorted. # # Hosts in either the hosts or backup lists can also be specified with # additional information, as follows: # # hosts=(hosta=(parameter1, param2=5), hostb=(param3), hostc) # # The host parameters are as follows: # # esmtp - speak ESMTP with the hosts if it is able. # onex - send ESMTP ONEX to the host if it supports it. # pipelining - send the ESMTP PIPELINING command to the host. # timeout - the number of seconds to wait when opening a connection # to the host # port - the port number to connect to, if different from the # usual SMTP port. # # If, instead of a host name, the string "@qmail" is used, Majordomo # will open a direct connection to the qmail-queue program and directly # inject the message into the qmail delivery system. This assumes, of # course, that you are running qmail. configset shop delivery_rules << ENDAAK ENDAAK # description # (undef) [string] # This is a short description of the list, used in the short listing. # It should be no more than 50 characters in order to fit on the average # terminal. If this is empty, the first line of 'description_long' is # used. If both are empty, the string "(no description)" is used. configset shop description = Mica Publicitate # description_long # (empty) [string_array] # This is the list description that appears in the long listing. Each line # should be no longer than 50 characters in order to fit on the average # terminal. If this variable is empty, the value of 'description' is used. # If both are empty, the string "(no description)" is used. configset shop description_long << ENDAAL ENDAAL # digest_index_format /subject,subject_author/ # (subject) [enum] # Selects one of the formats for each line in the index listing for the # digests. The 'subject' format consists simply of the subjects of the # messages. The 'subject_author' format, originally provided by Jeff # Wasilko, provides an index like the following: # # A subject [User ] # Another subject [Another User ] # A really, really, really, really, really really long subject # [A Verbose user ] configset shop digest_index_format = subject # digest_issues # (empty) [digest_issues] # A table of digest name, volume, issue. This is maintained # automatically by the digest system, and should be chane only with # care. # This variable is automatically maintained by Majordomo. Uncomment to change. # configset shop digest_issues << ENDAAM # digest : 1 : 2 # ENDAAM # digests # (empty) [digests] # # Data on the various digests that the list supports. A digest is # defined by a name, a description, and several pieces of data that tell # Majordomo when an issue should be generated. The following data can be given: # # name - A one-word name given to the digest. It is unwise to name # the digest "mime", "text" or "index". # # times - The times that digests are allowed to be created. Times are # specified as an integer from 0 to 23, the string "always" or # the string "never". The default is "always". # # minsizes - The minimum amount of data (measured in messages or # kilobytes) which must be collected before a digest will be # generated. The default is no minimum. # # maxsizes - The maximum size of digest that will be created. Specify # either messages or kilobytes or both as with minsizes. The # default is no maximum. # # maxage - If an article is older than this, a digest will be created # even if enough messages have not been collected. This # prevents messages from becoming "stale" on low traffic # lists. Specify hours like 12h, days like 4d and weeks like # 2w. The default is no maximum age. # # separate - The minimum amount of time that separates digests. # # minage - A digest will not be created if it most recent article is # younger than this. This is intended to prevent digest # creation in the middle of active discussion. The default # is no minimum age. # # deftype -- This specifies the type of digest that new subscribers get # by default. Currently only MIME, text and index digests are # supported. The default is MIME. # # Each digest is defined by two lines. The first contains data in the # following order, separated by vertical bars ('|') or colons: # # name | times | minsizes | maxsizes | maxage | separate | minage | deftype # # The second line holds a description of the digest. configset shop digests << ENDAAN digest | always | | | 1w | 1d | | MIME Digest ENDAAN # dup_lifetime # (28) [integer] # The number of days that entries in the duplicate databases will be # kept. Majordomo saves information about Message-ID:s and various # checksums of messages that pass through the list in order to filter # out duplicates. To limit database size and to cut down on the # possibility of false positives, these entries are periodically # trimmed after this number of days. configset shop dup_lifetime = 28 # faq_access /open,closed,list/ # (list) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop faq_access = list # file_search # (:$LANG ...) [list_array] # This provides a search-path mechanism for filename lookup. Entries are of # the form # # list:path # # where 'list' is the name of a list and path is the path within the # list's filespace. 'list' can be empty, in which case this list is used. # 'path' can be empty, in which case the root of the filespace is used. # Thus ':' refers to the top of the filespace of this list. # # To access files of another list, that list must must contain this # list's name in its file_share variable. If the referenced list does # not share with this list, the relevant entries will be ignored. configset shop file_search << ENDAAO :$LANG : ENDAAO # file_share # (empty) [list_array] # This should contain the names (one per line) of every list which is # allowed to access files from this list's filespace. configset shop file_share << ENDAAP ENDAAP # filedir # (undef) [directory] # The directory where the filespace for the list is kept. configset shop filedir = # get_access /open,closed,list/ # (list) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop get_access = list # index_access /open,closed,list/ # (open) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop index_access = open # info_access /open,closed,list/ # (open) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop info_access = open # inform # (empty) [inform] # This controls just what actions the list owner will be informed of and # what will be logged. The format of each line is: # # request | status | actions # # where request is subscribe, lists, post, etc., status is a comma # separated list of: # # succeed: perform the actions if the request succees. # fail: perform the actions if the request fails. # stall: perform the actions if the request is stalled. # all: always perform the actions # # and actions is a comma separated list of: # # ignore: completelu ignore the request # report: log the request for later reposting # inform: inform the owner immediately # # ignore overrides the others. # # If a request is not specified, the default behavior for subscribe and # unsubscribe is to inform on success, report otherwise. The default # behavior for all other requests is to report always. This # approximates the 1.9x behavior. # # Note that all actions are logged; this only affects which actions are # deemed important enough to send mail about and which will be reported. configset shop inform << ENDAAQ ENDAAQ # intro_access /open,closed,list/ # (list) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop intro_access = list # master_password # (shop.pass) [pw] # This is the master password for the list. A user having this password # can perform any list action and change any list data. configset shop master_password = ************ # max_header_line_length # (448) [integer] # Sets the maximum length of a single header in an unapproved message. # This can be used to prevent excessive CC'ing or to cut down on some # types of spam. Set to zero to disable length checks on single # headers. configset shop max_header_line_length = 448 # max_mime_header_length # (128) [integer] # Sets the maximum length of any single header in a MIME part. Some mail # reading programs are subject to crashing or security exploits when passed # messages with MIME headers that exceed a certain length. While these # mailers are definitely flawed and their users should contact the # manufacturers for upgrades, this variable is provided to filter out such # messages. # # Note that this setting does not implement any filtering for the security # exploits that can occur in the contents of the various parts of the body of # a message; this must be done with appropriate settings of taboo_body and # attachment_rules. (Filtering of HTML mail is recommended to help eliminate # exploits which lie in HTML tags.) configset shop max_mime_header_length = 128 # max_total_header_length # (2048) [integer] # Sets the maximum length of the headers in an unapproved message. Set to # zero to disable the total length check. configset shop max_total_header_length = 2048 # maxlength # (40000) [integer] # The maximum size of an unapproved message in characters. Set to zero to # disable the message length check. configset shop maxlength = 40000 # message_footer # (empty) [string_2darray] # This contains blocks of text, called footers, that can be added to # the beginning of outgoing messages. You can include multiple footers # here by separating them by blank lines. When a footer is to be # added, it is chosen at random from the footers given here. # # The following strings can be placed in footers; they well be # converted to the appropriate text when the footer is inserted into # the message: # # $LIST - the name of the list # $VERSION - the version of Majordomo # $SENDER - the person who sent the message # # Note that for multipart messages, footers appear as separate parts at # the end of the message and that footers are not added at all to single # part message that are not of type text/plain. (This avoids destroying # the content of structured messages.) # # The frequency with which footers appear can be controlled with the # variable "message_footer_frequency". configset shop message_footer << ENDAAR ENDAAR # message_footer_frequency # (100) [integer] # Controls how often a message_footer will be added to outgoing # messages. Set this to a number and on average footers will be added # to that percentage of messagees. If this is set to 100 or greater, # footers will always be added. If set to 0 or below, footers will # never be added (even if footers are defined). # # Note that this only makes sense if one or more footers have been set # in message_footer. Note also that this only controls the probability # that a footer will be added; the process itself is random. configset shop message_footer_frequency = 100 # message_fronter # (empty) [string_2darray] # This contains blocks of text, called fronters, that can be added to # the beginning of outgoing messages. You can include multiple fronters # here by separating them by blank lines. When a fronter is to be # added, it is chosen at random from the fronters given here. # # The following strings can be placed in fronters; they well be # converted to the appropriate text when the fronter is inserted into # the message: # # $LIST - the name of the list # $VERSION - the version of Majordomo # $SENDER - the person who sent the message # XXX (_SUBJECTS_) ??? # # Note that for multipart messages, fronters appear as separate parts at # the beginning of the message and that fronters are not added at all to # single part message that are not of type text/plain. (This avoids # destroying the content of structured messages.) # # The frequency with which fronters appear can be controlled with the # variable "message_fronter_frequency". configset shop message_fronter << ENDAAS ENDAAS # message_fronter_frequency # (100) [integer] # Controls how often a message_fronter will be added to outgoing # messages. Set this to a number and on average fronters will be added # to that percentage of messagees. If this is set to 100 or greater, # fronters will always be added. If set to 0 or below, fronters will # never be added (even if fronters are defined). # # Note that this only makes sense if one or more fronters have been set # in message_fronter. Note also that this only controls the probability # that a fronter will be added; the process itself is random. configset shop message_fronter_frequency = 100 # message_headers # (empty) [string_array] # These headers will be appended to the headers of the posted message. # The text is expanded before being used. The following expansion # tokens are defined: # $LIST - the name of the current list, # $SENDER - the sender as taken from the from line, # $SEQNO - the contents of the sequence_number variable, which is # automatically incremented each time a message is posted # $ARCHIVE - the number of this message in the archives # $VERSION - the version of Majordomo. configset shop message_headers << ENDAAT ENDAAT # moderate # (no) [bool] # If yes, all postings to the list must be approved by the moderator. configset shop moderate = # moderator # (undef) [word] # List messages requiring consultation will be sent to this address. # This is overridden by the addresses in 'moderators'. configset shop moderator = # moderator_group # (0) [integer] # List messages requiring consulataion will be sent to this many of the # addresses in 'moderators', chosen at random. If this is zero, the # message will be sent to all of the addresses in 'moderators'. configset shop moderator_group = # moderators # (empty) [address_array] # List messages requiring consultation will be sent to # 'moderator_group' (or all) of these addresses. Any of them may # approve or reject the message. configset shop moderators << ENDAAU ENDAAU # noadvertise # (empty) [regexp_array] # If the requestor name matches one of these regexps, then the list will # not be listed in the output of a lists command. Noadvertise overrides # advertise. configset shop noadvertise << ENDAAV ENDAAV # nonmember_flags # () [string] # A string containing the flags which apply to users who are not list members # when they send messages to the list. Only a very few flags make sense in # this case. They are: # # A - ackall # a - ackimportant configset shop nonmember_flags = # override_reply_to # (no) [bool] # If a reply-to header exists in the message and the list is configured # to add one of its own, should the existing one be deleted and replaced # with the list's? If set to no, the list will not add its reply-to # header if one is already present. configset shop override_reply_to = # owners # (empty) [address_array] # Who owns this list or majordomo installation? Majordomo will internally # forward mail received at the -owner address to all of these addresses. configset shop owners << ENDAAW majordomo@dnt.ro ENDAAW # passwords # (empty) [passwords] # A table of passwords, the actions they allow a user to perform, and an # optional list of user names which they are bound to. The table should # look like so: # # password1 : action, action, action # password2 : action, action : user@host.dom, blah@urk.org # # If no users are listed, the password can be used by all users. Any # addresses listed are put through the transformation and aliasing # processes before being used. # # The following actions are permitted: # # config_xyz - allows the user to view and alter the contents of # config variables in the group "xyz". # # XXX List all of the actions here! configset shop passwords << ENDAAX ENDAAX # precedence # (bulk) [word] # Put a precedence header with value into the outgoing message. configset shop precedence = bulk # purge_received # (no) [bool] # Remove all received lines before resending the message. configset shop purge_received = # quote_pattern # (/^( - | : | > | [a-z]+> )/xi) [regexp] # A regular expression used to match quoted text in message bodies. # This is used to generate the counts and percentages of quoted text. configset shop quote_pattern = /^( - | : | > | [a-z]+> )/xi # reply_to # (undef) [word] # Put a reply-to header with value into the outgoing message. If the # following strings appear here, they will be converted to the appropriate # text when the header is inserted into the message: # # $HOST - the hostname of the server (from the resend_host variable) # $LIST - the name of the list # $SENDER - the address of person who sent the message # $SEQNO - the message sequence number # # Note that a preexisting Reply-To: header will not be replaced unless # override_reply_to is true. configset shop reply_to = # resend_host # (list.dnt.ro) [word] # The host name that is appended to all address strings specified for # resend. configset shop resend_host = list.dnt.ro # restrict_post # (empty) [restrict_post] # # If defined only addresses belonging to one of the listed sublists will # be allowed to post to the list. This variable's function is # completely encapsulated within the access_rules mechanism, but it # remains for backwards compatibility and because it's simpler to use. # # This is an array variable, but for backwards compatibility the first # item is split on spaces, tabs, and colons. configset shop restrict_post << ENDAAY ENDAAY # sender # (shop-owner) [address] # The envelope and sender address for the resent mail. This string has # "@" and the value of resend_host appended to it to make a complete # address. For majordomo, it provides the sender address for the # welcome mail message generated as part of the subscribe command. configset shop sender = shop-owner # sequence_number # (1) [integer] # This is the sequence number used to number messages which pass through the # list. It is automatically incremented by one for each message. It may be # manually set here. # This variable is automatically maintained by Majordomo. Uncomment to change. # configset shop sequence_number = 27 # subject_prefix # (undef) [string] # This word will be prefixed to the subject line, if it is not already # in the subject. The text is expanded before being used. The following # expansion tokens are defined: # $LIST - the name of the current list # $SEQNO - the contents of the sequence_number variable, which is # automatically incremented each time a message is posted # $VERSION - the version of Majordomo configset shop subject_prefix = [$LIST:$SEQNO] # subscribe_policy /open,closed,auto,open+confirm,closed+confirm,auto+confirm/ # (open+confirm) [enum] # One of three values: open, closed, auto; plus an optional modifier: # '+confirm'. Open allows people to subscribe themselves to the list, # but attempts to subscribe addresses diferent than where the request is # coming from will require approval. Auto allows anybody to subscribe # anybody to the list without maintainer approval. Closed requires # maintainer approval for all subscribe requests to the list. Adding # '+confirm', (i.e. 'open+confirm') will cause majordomo to send a reply # back to the subscriber which includes a authentication number which # must be sent back in with another subscribe command. configset shop subscribe_policy = open+confirm # taboo_body # (empty) [taboo_body] # If any line of the body matches one of these regexps, then the message # will be bounced for review. XXX Ugh. configset shop taboo_body << ENDAAZ ENDAAZ # taboo_headers # (empty) [taboo_headers] # If any of the headers matches one of these regexps, then the message # will be bounced for review. XXX Ugh. configset shop taboo_headers << ENDABA ENDABA # token_lifetime # (7) [integer] # The number of days that a token will be allowed to live without being # acknowledged (either approved or rejected). Tokens existing longer # than this many days are deleted at every daily trigger. configset shop token_lifetime = 7 # token_remind # (4) [integer] # If a token exists longer than this many days, a reminder message will # be sent. If this is unset or zero, no reminders will be sent. configset shop token_remind = 4 # unsubscribe_policy /open,closed,auto/ # (open) [enum] # One of three values: open, closed, auto. Open allows people to # unsubscribe themselves from the list. Auto allows anybody to # unsubscribe anybody to the list without maintainer approval. Closed # requires maintainer approval for all unsubscribe requests to the list. configset shop unsubscribe_policy = open # welcome # (yes) [bool] # If this is on, new subscribers (or registered users) will be sent a welcome # message. configset shop welcome = 1 # welcome_files # (Welcome to the $LIST mailing list! ...) [welcome_files] # # A table containing a list of files and descriptions that should be # sent to new subscribers. # # Each table record takes two lines. The first should be an explanatory # message, which will go in the subject or content-description header as # appropriate. (If this is empty, the file's description will be used.) # The second is broken into fields by ":" or "|". # # The first field is the name of the file, in the file space of the list. # # The second should be either "N", meaning that the file will be sent as # a separate piece of mail, or "P", meaning that the file will be # attached to the previous file. The default is "N". In addition, an # "S" can be added, indicating that the file should undergo variable # substitution. configset shop welcome_files << ENDABB Welcome to the $LIST mailing list! welcome | NS List introductory information info | PS ENDABB # which_access /open,closed,list/ # (open) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop which_access = list # who_access /open,closed,list/ # (open) [enum] # One of three values: open, list, closed. Open allows anyone access to this # command. List allows only list members access, while closed completely # disables the command for everyone. configset shop who_access = list # whoami # (shop) [address] # What address do users send requests to? configset shop whoami = shop # whoami_owner # (shop-owner) [address] # Where to bounces from the whoami address go? configset shop whoami_owner = shop-owner From majordomo-workers-owner Wed Jul 7 07:19:40 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA12867; Wed, 7 Jul 1999 07:12:23 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA12860 for ; Wed, 7 Jul 1999 07:12:18 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id JAA31473; Wed, 7 Jul 1999 09:18:09 -0500 To: majordomo-workers@greatcircle.com, Stefanita Vilcu Subject: Re: majordomo 2 does not restrict posts? References: From: Jason L Tibbitts III Date: 07 Jul 1999 09:18:09 -0500 In-Reply-To: Stefanita Vilcu's message of "Tue, 6 Jul 1999 01:36:10 +0300 (EEST)" Message-ID: Lines: 32 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk SV> It seems to work ok but it is not restricting the posts only to the SV> list members. On the moderated lists it is ok. I use the defaut SV> configuration for an unmoderated, open+confirm list access. I think I SV> am wrong, but where? The default configuration does not restrict posting to list members, just as Majordomo1 has always done. I see nothing in your configuration that would do any restriction whatsoever. So I'm confused. Are you saying that you have made configuration changes that you expect to restrict posting? If so, I can't find them. Or are you asking how to make the necessary configuration changes? If so, there are two ways: put the name of the list in the restrict_post variable: restrict_post = shop or put the following in access_rules: access_rules << END post consult !@MAIN END The latter causes the list owner to be consulted when the posting address is not on the subscriber list. - J< From majordomo-workers-owner Sun Jul 11 11:18:20 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19713; Sun, 11 Jul 1999 11:09:21 -0700 (PDT) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA19706 for ; Sun, 11 Jul 1999 11:09:15 -0700 (PDT) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by plab.ku.dk (8.9.1/8.9.1) with ESMTP id UAA20399 for ; Sun, 11 Jul 1999 20:12:16 +0200 (CEST) Received: (from tobez@localhost) by lion.plab.ku.dk (8.9.3/8.9.3) id UAA40192 for majordomo-workers@greatcircle.com; Sun, 11 Jul 1999 20:09:57 +0200 (CEST) (envelope-from tobez) Date: Sun, 11 Jul 1999 20:09:57 +0200 From: Anton Berezin To: majordomo-workers@greatcircle.com Subject: $fromters and $footers aren't expanded correctly with substitute_vars_string() Message-ID: <19990711200957.A40136@lion.plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hello, I think this can be qualified as a bug report. $LIST and friends are not expanded in Mj::Resend.pm::_add_fters(). No wonder, actually, since $foot and $front are references to arrays (if they are defined), and they are passed to substitute_vars_string() which expects a string. This can easily be fixed; in two places actually - either in _add_fters() by implementing a little loop, like this (the patch is relative to the sources cvs'ed five minutes ago): --- /home/tobez/src/majordomo/lib/Mj/Resend.pm.orig Sun Jul 11 19:51:40 1999 +++ /home/tobez/src/majordomo/lib/Mj/Resend.pm Sun Jul 11 19:54:39 1999 @@ -1281,8 +1281,16 @@ return unless $front || $foot; # Substitute values - $front = $self->substitute_vars_string($front, $subs) if $front; - $foot = $self->substitute_vars_string($foot, $subs) if $foot; + if ($front) { + for (@$front) { + $_ = $self->substitute_vars_string($_, $subs); + } + } + if ($foot) { + for (@$foot) { + $_ = $self->substitute_vars_string($_, $subs); + } + } # We take different actions if the message is multipart if ($ent->is_multipart) { Another way of doing this is to make substitute_vars_string() aware of array refs (this might be more useful in the future, I think): --- /home/tobez/src/majordomo/lib/Majordomo.pm.orig Sun Jul 11 20:04:53 1999 +++ /home/tobez/src/majordomo/lib/Majordomo.pm Sun Jul 11 20:05:01 1999 @@ -519,6 +519,14 @@ my $subs = shift; my $i; + if ( ref $str eq 'ARRAY') { + for (@$str) { + # the recursion should not harm here + $_ = $self->substitute_vars_string($_, $subs); + } + return $str; + } + for $i (keys %$subs) { # Don't substitute after backslashed $'s $str =~ s/([^\\]|^)\$\Q$i\E(\b|$)/$1$subs->{$i}/g; I did not actually want to duplicate the s/// here, so I went with a recursive approach. Hope this is fine. Thanks for a great product - I think mj2 is destined to be waay better (and better managable) than mj1! -- Anton Berezin The Protein Laboratory, University of Copenhagen From majordomo-workers-owner Sun Jul 11 13:17:44 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA20919; Sun, 11 Jul 1999 13:17:34 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA20912 for ; Sun, 11 Jul 1999 13:17:29 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id PAA08282; Sun, 11 Jul 1999 15:20:22 -0500 To: majordomo-workers@greatcircle.com, Anton Berezin Subject: Re: $fromters and $footers aren't expanded correctly with substitute_vars_string() References: <19990711200957.A40136@lion.plab.ku.dk> From: Jason L Tibbitts III Date: 11 Jul 1999 15:20:22 -0500 In-Reply-To: Anton Berezin's message of "Sun, 11 Jul 1999 20:09:57 +0200" Message-ID: Lines: 13 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "AB" == Anton Berezin writes: AB> Hello, I think this can be qualified as a bug report. Yes, for a dumb bug. Thanks for the fix; I have applied the patch to make substitute_vars_string recursive since it may come in handy later. It should show up in CVS when I commit later this evening. Since you obviously had to delve into the code to figure this out, can you relate your experience? I'm interested in how difficult it was for you to find the fix. - J< From majordomo-workers-owner Sun Jul 11 13:32:46 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA21006; Sun, 11 Jul 1999 13:29:57 -0700 (PDT) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA20999 for ; Sun, 11 Jul 1999 13:29:51 -0700 (PDT) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by plab.ku.dk (8.9.1/8.9.1) with ESMTP id WAA21408; Sun, 11 Jul 1999 22:32:53 +0200 (CEST) Received: (from tobez@localhost) by lion.plab.ku.dk (8.9.3/8.9.3) id WAA40941; Sun, 11 Jul 1999 22:30:34 +0200 (CEST) (envelope-from tobez) Date: Sun, 11 Jul 1999 22:30:34 +0200 From: Anton Berezin To: Jason L Tibbitts III Cc: majordomo-workers@greatcircle.com Subject: Re: $fromters and $footers aren't expanded correctly with substitute_vars_string() Message-ID: <19990711223034.F40213@lion.plab.ku.dk> References: <19990711200957.A40136@lion.plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jason L Tibbitts III on Sun, Jul 11, 1999 at 03:20:22PM -0500 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Sun, Jul 11, 1999 at 03:20:22PM -0500, Jason L Tibbitts III wrote: > >>>>> "AB" == Anton Berezin writes: > > AB> Hello, I think this can be qualified as a bug report. > > Yes, for a dumb bug. Thanks for the fix; I have applied the patch to > make substitute_vars_string recursive since it may come in handy > later. It should show up in CVS when I commit later this evening. Thanks for the fast responce. > Since you obviously had to delve into the code to figure this out, can > you relate your experience? I'm interested in how difficult it was > for you to find the fix. Hmm, basically: $ cd /usr/local/site/majordomo/lib $ grep message_footer **/*(.) <-- that's zshism $ less Mj/Resend.pm .. looking .. $ less Majordomo.pm .. looking more .. .. saying ahhhaa! .. Though, I would qualify myself as a rather experienced with Perl 5. :-) What I like about mj2 is that it is much better structured [than mj1], so it should not be difficult for a person with basic p5 modules knowledge to find such things as this one. Regards, -- Anton Berezin The Protein Laboratory, University of Copenhagen From majordomo-workers-owner Tue Jul 13 08:19:06 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA19569; Tue, 13 Jul 1999 08:14:40 -0700 (PDT) Received: from uplift.swm.pp.se (swm.pp.se [194.218.202.226]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA19562 for ; Tue, 13 Jul 1999 08:14:34 -0700 (PDT) Received: from localhost (jesper@localhost) by uplift.swm.pp.se (8.9.3/8.9.3) with ESMTP id RAA23328; Tue, 13 Jul 1999 17:17:31 +0200 Date: Tue, 13 Jul 1999 17:17:31 +0200 (MEST) From: Jesper Maartenson X-Sender: jesper@uplift.swm.pp.se To: majordomo-workers@greatcircle.com cc: tibbs@hpc.uh.edu Subject: majordomo2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Problem when trying to install majordomo2: [jesper@uplift majordomo]$ perl Makefile.PL Checking for Sys::Syslog and syslog.ph Constant subroutine __need___va_list undefined at /usr/lib/perl5/5.00503/i386-linux/stdarg.ph line 9. What have I missed? ________________________ _______ http://jesper.maartenson.net http://kanalen.org From majordomo-workers-owner Tue Jul 13 08:33:28 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA19797; Tue, 13 Jul 1999 08:30:04 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA19774; Tue, 13 Jul 1999 08:29:50 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA26083; Tue, 13 Jul 1999 10:32:54 -0500 To: SRE Cc: majordomo-users@GreatCircle.COM, majordomo-workers@GreatCircle.COM Subject: Re: From Headers References: <199907121551.KAA20519@mirage.texasmicro.com> <3.0.5.32.19990712173346.00a404a0@pop.climber.org> From: Jason L Tibbitts III Date: 13 Jul 1999 10:32:54 -0500 In-Reply-To: SRE's message of "Mon, 12 Jul 1999 17:33:46 -0700" Message-ID: Lines: 19 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "S" == SRE writes: S> I'll second Swenson's motion! I think a "full name" should be used S> whenever it is available, instead of just an email address. I _strongly_ disagree with this. The address the user supplied in their From: header when they sent the message is to be preferred over _everything else_ unless there is some special situation (i.e. the user specifically sets something or the list is anonymizing). I'm discussing a feature in the context of these special situations. The suggestion that this should be a general thing is not something I want to consider. I was afraid that the "gratuitously rewrite everything" bit would spring up here; I want to make it clear that I'm trying to cover one small set of special situations. As for being a per-list user-overridaeable settings, it would work just like any other flag: the owner sets the default and the user can change it. - J< From majordomo-workers-owner Tue Jul 13 08:48:24 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA19919; Tue, 13 Jul 1999 08:38:06 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA19891 for ; Tue, 13 Jul 1999 08:37:57 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA26136; Tue, 13 Jul 1999 10:40:58 -0500 To: Jesper Maartenson Cc: majordomo-workers@greatcircle.com Subject: Re: majordomo2 References: From: Jason L Tibbitts III Date: 13 Jul 1999 10:40:58 -0500 In-Reply-To: Jesper Maartenson's message of "Tue, 13 Jul 1999 17:17:31 +0200 (MEST)" Message-ID: Lines: 10 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "JM" == Jesper Maartenson writes: JM> Constant subroutine __need___va_list undefined at JM> /usr/lib/perl5/5.00503/i386-linux/stdarg.ph line 9. Isn't this just a warning? It comes from a Perl bug which I can't fix in Majordomo but it shouldn't actually hurt anything. Is it causing you problems? - J< From majordomo-workers-owner Tue Jul 13 10:47:56 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA21163; Tue, 13 Jul 1999 10:41:22 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA21156 for ; Tue, 13 Jul 1999 10:41:17 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id MAA27176; Tue, 13 Jul 1999 12:44:23 -0500 To: steves@texasmicro.com Cc: majordomo-workers@greatcircle.com Subject: Re: From Headers References: <199907131644.LAA05253@mirage.texasmicro.com> From: Jason L Tibbitts III Date: 13 Jul 1999 12:44:23 -0500 In-Reply-To: steve swenson's message of "Tue, 13 Jul 1999 11:44:51 -0500" Message-ID: Lines: 34 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "ss" == steve swenson writes: ss> Maybe a title command? Have it check and see if the user is a member ss> of the given list. Also Might have the use of the command have ss> restricted access and available to third party. I think that's a bit above what I was planning to implement. For option #2, the only interface would be through a user flag: set listname rewritefrom set listname norewritefrom For option #3, the interface would be something like set listname rewritefrom Some Address ss> For example only the Personnel office(if so designated) could change ss> titles. Other lists might allow open use of the command for use as ss> "handles". Kinda like your Open, List Restricted options for ss> Majordomo1. Access control would be through the generic Majordomo2 access restriction mechanism. ss> title listname useraddress Comment_for_From_Header I don't think a whole new command is warranted when this is just another user setting. Plus any address argument would have to be in the form of a legal RFC822 address. You cannot independently set a comment on an address, as comments come in many forms and can appear in various places in the address. - J< From majordomo-workers-owner Tue Jul 13 11:32:56 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA21586; Tue, 13 Jul 1999 11:19:23 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA21579 for ; Tue, 13 Jul 1999 11:19:17 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id NAA27369; Tue, 13 Jul 1999 13:22:22 -0500 To: steves@texasmicro.com Cc: majordomo-workers@greatcircle.com Subject: Re: From Headers References: <199907131758.MAA05350@mirage.texasmicro.com> From: Jason L Tibbitts III Date: 13 Jul 1999 13:22:22 -0500 In-Reply-To: steve swenson's message of "Tue, 13 Jul 1999 12:58:09 -0500" Message-ID: Lines: 40 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "ss" == steve swenson writes: ss> If the comment field isn't in this format couldn't we have Majordomo ss> convert it... Here is a legal RFC822 address which Majordomo understands and can deal with just fine: Jason (tibbs) Tibbitts (Me) Please tell me how to convert it. I don't think you want it turned into: Jason tibbs Tibbitts da man ematics Me These things are not easy. If what was a simple feature request turns into a mess of special cases and bizarre requirements I'll drop it rather quickly. As it stands, it's one of: User sets a flag and when Majordomo sees their From: address it is rewritten into the form they supplied when they joined. or User chooses a legal (though not necessarily deliverable) RFC822 address; when Majordomo sees their From: address it is rewritten. Note that these two options were chosen because they're easy to implement (the first is around ten lines) and simple to understand. When you get into converting addresses into different forms, just modifying the comments, and other such things then it's not simple even before you consider that RFC822 lets users do some very disgusting things that _must_ be supported. Note also that there will eventually be functionality to change the address that you are subscribed as; that is completely orthogonal from the current discussion. - J< From majordomo-workers-owner Tue Jul 13 13:38:30 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA23801; Tue, 13 Jul 1999 13:24:35 -0700 (PDT) Received: from uplift.swm.pp.se (swm.pp.se [194.218.202.226]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA23793 for ; Tue, 13 Jul 1999 13:24:23 -0700 (PDT) Received: from localhost (jesper@localhost) by uplift.swm.pp.se (8.9.3/8.9.3) with ESMTP id WAA25721 for ; Tue, 13 Jul 1999 22:27:27 +0200 Date: Tue, 13 Jul 1999 22:27:27 +0200 (MEST) From: Jesper Maartenson X-Sender: jesper@uplift.swm.pp.se To: majordomo-workers@greatcircle.com Subject: mj2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Just got mj2 to work, and it seems like a very powerful piece of software. One thing though, no way to delete lists this far? ________________________ _______ http://jesper.maartenson.net http://kanalen.org From majordomo-workers-owner Tue Jul 13 13:49:11 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA23945; Tue, 13 Jul 1999 13:29:48 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA23938; Tue, 13 Jul 1999 13:29:43 -0700 (PDT) Received: from ee-nt (eckert@netcom9.netcom.com [192.100.81.119]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id NAA26965; Tue, 13 Jul 1999 13:33:01 -0700 (PDT) Message-Id: <3.0.5.32.19990713133319.009cd540@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 13 Jul 1999 13:33:19 -0700 To: Jason L Tibbitts III From: SRE Subject: Re: From Headers Cc: majordomo-users@GreatCircle.COM, majordomo-workers@GreatCircle.COM In-Reply-To: References: <199907121551.KAA20519@mirage.texasmicro.com> <3.0.5.32.19990712173346.00a404a0@pop.climber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 10:32 AM 7/13/99 -0500, Jason L Tibbitts III wrote: >I _strongly_ disagree with this. The address the user supplied in their >From: header when they sent the message is to be preferred over _everything >else_ unless there is some special situation (i.e. the user specifically >sets something or the list is anonymizing). I'm discussing a feature in >the context of these special situations. OK, I'm just suggesting another place to get the replacement text. I agree the "From:" header should be the first choice, but we're talking about alternatives... If you're allowing the "From:" header to be replaced, one possible option is to let the user store new text. Another possible option is to use the global registry. Either will work for me, because I can just write a script that reads the registry and stuffs the user-supplied-text field of the new command. That would be a big help, with or without a way to directly access the registry. From majordomo-workers-owner Tue Jul 13 14:06:17 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA23873; Tue, 13 Jul 1999 13:27:46 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id NAA23863 for majordomo-workers@greatcircle.com; Tue, 13 Jul 1999 13:27:43 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA08777; Mon, 12 Jul 1999 18:15:47 -0700 (PDT) Received: from ee-nt (eckert@netcom12.netcom.com [192.100.81.124]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id SAA21338; Mon, 12 Jul 1999 18:18:43 -0700 (PDT) Message-Id: <3.0.5.32.19990712173346.00a404a0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 12 Jul 1999 17:33:46 -0700 To: tibbs@hpc.uh.edu From: SRE Subject: Re: From Headers Cc: majordomo-users@GreatCircle.COM, majordomo-workers@GreatCircle.COM In-Reply-To: References: <199907121551.KAA20519@mirage.texasmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I'll second Swenson's motion! I think a "full name" should be used whenever it is available, instead of just an email address. Could this be set on a site basis and overridden per-list? Mj2 has a "register" command, but the comments stored there are not used when showing who is subcribed to a list. Consider changing that when/if you change the From field in posts. Also consider providing a way to update the comment field without leaving/joining each list (perhaps each subscribe command should update it, perhaps a new register command should update it, perhaps there should be a way to replace one complete address with another?) I'd like the global registry to be the universal lookup table that provides a simple and effective way to figure out who did what and who is who... both for list subscribers and for list managers! SRE ---------------------------------------------------- At 01:45 PM 7/11/99 -0500, steve swenson wrote: >I would like to have Majordomo rewrite the From:header to utilize >comments in the lists/listname file. The comments contain titles and real >names of members from many different email accounts. At 12:17 PM 7/12/99 -0500, tibbs@hpc.uh.edu wrote on majordomo-users: >I need to think further about how to implement what you're asking for, but >I can see several possible methods: > >1) A per-list config, all From: addresses belonging to members are > rewritten to the full address that they joined with. > >2) A per-user setting, doing the same. > >3) A per-user setting; users can choose exactly the address they want their > From: rewritten to. > >I'll axe #1 now as too coarse-grained. #2 is easy for me to implement and >probably suits your needs. #3 opens up some interesting possibilities. It >is marginally more difficult for me to implement (since there needs to be >an interface for setting the rewritten address) but it shouldn't be too >bad. Ideas? > >I should probably be doing this on majordomo-workers, but what the heck. >Be sure to direct followups appropriately if discussing details. > > - J< > > From majordomo-workers-owner Tue Jul 13 14:49:17 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA24636; Tue, 13 Jul 1999 14:33:07 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA24619; Tue, 13 Jul 1999 14:32:54 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id QAA28662; Tue, 13 Jul 1999 16:36:00 -0500 To: SRE Cc: majordomo-users@GreatCircle.COM, majordomo-workers@GreatCircle.COM Subject: Re: From Headers References: <199907121551.KAA20519@mirage.texasmicro.com> <3.0.5.32.19990712173346.00a404a0@pop.climber.org> <3.0.5.32.19990713133319.009cd540@pop.climber.org> From: Jason L Tibbitts III Date: 13 Jul 1999 16:35:59 -0500 In-Reply-To: SRE's message of "Tue, 13 Jul 1999 13:33:19 -0700" Message-ID: Lines: 26 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "S" == SRE writes: S> OK, I'm just suggesting another place to get the replacement text. I S> agree the "From:" header should be the first choice, but we're talking S> about alternatives... The point I was trying to make was that things like From: shouldn't be rewritten unless the list is somehow "special" or the user has requested it. S> If you're allowing the "From:" header to be replaced, one possible S> option is to let the user store new text. That's #3 in my previous messages. S> Another possible option is to use the global registry. Why the global database? This is most definitely a per-list setting. For instance, I might want to change my address to Jason Tibbitts (Moderator) for lists that I moderate. (Of course, my mail software lets me do that already, but few do.) - J< From majordomo-workers-owner Tue Jul 13 15:20:29 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA25172; Tue, 13 Jul 1999 15:14:35 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA25165 for ; Tue, 13 Jul 1999 15:14:30 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id RAA28868; Tue, 13 Jul 1999 17:17:38 -0500 To: Chuck Milam Cc: Jesper Maartenson , majordomo-workers@greatcircle.com Subject: Re: majordomo2 References: From: Jason L Tibbitts III Date: 13 Jul 1999 17:17:38 -0500 In-Reply-To: Chuck Milam's message of "Tue, 13 Jul 1999 17:15:54 -0500 (CDT)" Message-ID: Lines: 10 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "CM" == Chuck Milam writes: CM> I get this warning all the time with my MJ2 installation, doesn't seem CM> to hurt anything here. I am pretty sure that you can just comment out line nine of that file. It seems that this is a problem on any platform running a recent perl and glibc; h2ph misparses one of the header files. - J< From majordomo-workers-owner Tue Jul 13 15:34:48 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA25137; Tue, 13 Jul 1999 15:10:26 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA25128 for ; Tue, 13 Jul 1999 15:10:20 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id RAA28837; Tue, 13 Jul 1999 17:13:30 -0500 To: majordomo-workers@greatcircle.com Subject: Re: mj2 References: From: Jason L Tibbitts III Date: 13 Jul 1999 17:13:30 -0500 In-Reply-To: Jesper Maartenson's message of "Tue, 13 Jul 1999 22:27:27 +0200 (MEST)" Message-ID: Lines: 15 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "JM" == Jesper Maartenson writes: JM> One thing though, no way to delete lists this far? Currently there is no way to do this. It's a bit more complicated than creating them because you have to worry about any users which might be on those lists and anything like archives which might exist for that list. The situation is actually pretty simple if the list is empty and has no files: just delete the directory and remove the aliases. If you need this functionality I can probably knock out a naive implementation over the weekend. - J< From majordomo-workers-owner Tue Jul 13 15:50:36 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA25159; Tue, 13 Jul 1999 15:12:35 -0700 (PDT) Received: from milam.acstaff.uwosh.edu (milam.acstaff.uwosh.edu [141.233.129.180]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id PAA25150 for ; Tue, 13 Jul 1999 15:12:30 -0700 (PDT) Received: (qmail 3661 invoked from network); 13 Jul 1999 22:15:54 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 13 Jul 1999 22:15:54 -0000 Date: Tue, 13 Jul 1999 17:15:54 -0500 (CDT) From: Chuck Milam X-Sender: milam@milam.acstaff.uwosh.edu To: Jason L Tibbitts III cc: Jesper Maartenson , majordomo-workers@greatcircle.com Subject: Re: majordomo2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Tue, 13 Jul 1999, Jason L Tibbitts III wrote: > JM> Constant subroutine __need___va_list undefined at > JM> /usr/lib/perl5/5.00503/i386-linux/stdarg.ph line 9. > > Isn't this just a warning? It comes from a Perl bug which I can't fix in > Majordomo but it shouldn't actually hurt anything. I get this warning all the time with my MJ2 installation, doesn't seem to hurt anything here. -- Chuck Milam - milam@uwosh.edu I.T. Division - Academic Computing University of Wisconsin Oshkosh From majordomo-workers-owner Wed Jul 14 01:26:36 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id AAA01160; Wed, 14 Jul 1999 00:57:59 -0700 (PDT) Received: from rina.torah.org (rina.torah.org [207.226.84.142]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id AAA01153 for ; Wed, 14 Jul 1999 00:57:54 -0700 (PDT) Received: from localhost (brozen@localhost) by rina.torah.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id EAA23888 for ; Wed, 14 Jul 1999 04:01:23 -0400 Date: Wed, 14 Jul 1999 11:01:23 +0300 (IDT) From: Brock Rozen To: Majordomo Workers List Subject: Deleting lists Message-ID: X-URL: http://www2.torah.org/~brozen/ X-Backup: Disable MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi, (Wow, it's been a long time since I've posted here....) Let's figure out what issues have to be dealt with in deleting lists. I see a few: Actually deleting it (removing list files and aliases) Notifying subscribers (and allowing a quiet option) Changing aliases to have messages sent to the list-owner for a period of time (even after deletion), for lists that have moved to a different system Archives (allow deletion or keeping them around) Allowing them to still be kept means that mj has to allow for retrieval of "non-list" (because it's no longer a list) archives that's not gonna be fun forwarding un/subscribe commands - again for lists that have moved location Anything else? And, IMHO, only the mj system owner can remove a list. list-owner's should NOT have this functionality. -- Brock Rozen brozen@torah.org Director of Technical Services (410) 602-1350 Project Genesis http://www.torah.org/ From majordomo-workers-owner Wed Jul 14 01:35:48 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id BAA01366; Wed, 14 Jul 1999 01:03:36 -0700 (PDT) Received: from mibi02.meb.uni-bonn.de (mibi02.meb.uni-bonn.de [131.220.21.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id BAA01344 for ; Wed, 14 Jul 1999 01:03:22 -0700 (PDT) Received: (from ernst@localhost) by mibi02.meb.uni-bonn.de (8.9.2/8.9.2/Debian/GNU) id KAA30775; Wed, 14 Jul 1999 10:10:54 +0200 (CEST) Date: Wed, 14 Jul 1999 10:10:54 +0200 (CEST) Message-Id: <199907140810.KAA30775@mibi02.meb.uni-bonn.de> X-Authentication-Warning: mibi02.meb.uni-bonn.de: ernst set sender to ernst@mibi02.meb.uni-bonn.de using -f From: Ernst Molitor To: milam@uwosh.edu CC: tibbs@math.uh.edu, jesper@maartenson.net, majordomo-workers@GreatCircle.COM In-reply-to: (message from Chuck Milam on Tue, 13 Jul 1999 17:15:54 -0500 (CDT)) Subject: Re: majordomo2 CC: Ernst Molitor References: Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi, > JM> Constant subroutine __need___va_list undefined at > JM> /usr/lib/perl5/5.00503/i386-linux/stdarg.ph line 9. I've seen this warning, too; after recompiling Perl (I have updated the glibc to 2.1.1 some time ago, and the Perl binary had been compiled against a former version of glibc), the message did not show up again... Best regards, Ernst From majordomo-workers-owner Wed Jul 14 01:50:41 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id BAA02548; Wed, 14 Jul 1999 01:45:08 -0700 (PDT) Received: from uplift.swm.pp.se (swm.pp.se [194.218.202.226]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id BAA02533 for ; Wed, 14 Jul 1999 01:44:57 -0700 (PDT) Received: from localhost (jesper@localhost) by uplift.swm.pp.se (8.9.3/8.9.3) with ESMTP id KAA25627 for ; Wed, 14 Jul 1999 10:48:04 +0200 Date: Wed, 14 Jul 1999 10:48:04 +0200 (MEST) From: Jesper Maartenson X-Sender: jesper@uplift.swm.pp.se To: majordomo-workers@greatcircle.com Subject: using BOTh sendmail and qmail. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk In my currect majordomo1-config I use sendmail for incoming mail and send out mail with qmail. How can I do this in a good way with mj2? ________________________ _______ http://jesper.maartenson.net http://kanalen.org From majordomo-workers-owner Wed Jul 14 07:54:08 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA07761; Wed, 14 Jul 1999 07:45:04 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA07746 for ; Wed, 14 Jul 1999 07:44:57 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id JAA01104; Wed, 14 Jul 1999 09:48:00 -0500 To: majordomo-workers@greatcircle.com, Jesper Maartenson Subject: Re: using BOTh sendmail and qmail. References: From: Jason L Tibbitts III Date: 14 Jul 1999 09:47:59 -0500 In-Reply-To: Jesper Maartenson's message of "Wed, 14 Jul 1999 10:48:04 +0200 (MEST)" Message-ID: Lines: 36 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "JM" == Jesper Maartenson writes: JM> In my currect majordomo1-config I use sendmail for incoming mail and JM> send out mail with qmail. OK. JM> How can I do this in a good way with mj2? Obviously it's not going to be handled automatically but it should be trivial to set up. Majordomo talks via SMTP to the mailer (although there is some untested special qmail code in Mj::Deliver::QQEnvelope) so you can't just change the name of an executable that gets called. You can, however, specify the port (or, heck, even the host or a list of hosts) to use for outgoing SMTP in the delivery_rules variable. So tell Majordomo it's using sendmail (because it uses that to construct alias files and such) and configure the delivery methods to your liking using delivery_rules. Perhaps you could run qmail on, say, port 26 and set delivery_rules like so: configset listname delivery_rules <; Wed, 14 Jul 1999 08:00:24 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA01175; Wed, 14 Jul 1999 10:03:38 -0500 To: majordomo-workers@greatcircle.com Subject: Re: Deleting lists References: From: Jason L Tibbitts III Date: 14 Jul 1999 10:03:38 -0500 In-Reply-To: Brock Rozen's message of "Wed, 14 Jul 1999 11:01:23 +0300 (IDT)" Message-ID: Lines: 54 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "BR" == Brock Rozen writes: BR> Let's figure out what issues have to be dealt with in deleting lists. But note also the importance of not over-thinking things. BR> Actually deleting it (removing list files and aliases) Which is basically the only functionality that the "delete list" command needs to handle. BR> Notifying subscribers (and allowing a quiet option) That's an orthogonal issue. The owner can just post a message if they so desire. Eventually I'll write that mail-merge command so that you can send out a "personalized" message. BR> Changing aliases to have messages sent to the list-owner for a period BR> of time (even after deletion), for lists that have moved to a different BR> system I don't agree. The list owner can set this up ahead of time by other perfectly valid means. When the actual "delete list" command is run, the list should be deleted, messages to it should bounce, etc. If you can still mail to it (i.e. it still has aliases and an owner) then it has a configuration and hasn't been deleted. Note also that we provide the 'forward' mechanism to automatically handle lists that have moved to another system (by actually forwarding the messages there). BR> Archives (allow deletion or keeping them around) Again, if the archives are still retrievable through Majordomo then the list must still exist. Sure, it may not have any subscribers and you can't post to it but it is still a perfectly valid list. BR> Anything else? Well, much, much less than that. The naive implementation deletes the list directory.. The complex implementation checks to see that the list has no members first. All other functionality that you mention belongs somewhere else. BR> And, IMHO, only the mj system owner can remove a list. list-owner's BR> should NOT have this functionality. I think I agree, especially since I'll probably just implement this as part of the createlist command: createlist-delete listname - J< From majordomo-workers-owner Wed Jul 14 10:04:31 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA09315; Wed, 14 Jul 1999 10:01:14 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA09308 for ; Wed, 14 Jul 1999 10:01:09 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id MAA02197; Wed, 14 Jul 1999 12:04:14 -0500 To: goodwin@apple.com Cc: majordomo-workers@greatcircle.com Subject: Re: majordomo2 install problem. References: <378CC040.5E42E4E2@apple.com> From: Jason L Tibbitts III Date: 14 Jul 1999 12:04:13 -0500 In-Reply-To: Larry Goodwin's message of "Wed, 14 Jul 1999 09:52:16 -0700" Message-ID: Lines: 17 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "LG" == Larry Goodwin writes: LG> I am installing Majordomo2 release "majordomo-0.1199906210" on LG> AIX 4.1.5 and get to make install and get these errors. Hmmm. I don't know that anyone's run it on AIX before, though I don't think that there would be problems. LG> Can't find site config file blueske/SITE/config.pl: No such file or LG> directory That's the problem; now, tell us somethig about this file. Does it exist? What are its permissions? It looks odd that it isn't an absolute path; did you not supply absolute paths to any of the configuration questions? - J< From majordomo-workers-owner Wed Jul 14 12:48:06 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA11040; Wed, 14 Jul 1999 12:47:39 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA11033 for ; Wed, 14 Jul 1999 12:47:34 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id OAA03381; Wed, 14 Jul 1999 14:50:41 -0500 To: goodwin@apple.com Cc: majordomo-workers@greatcircle.com Subject: Re: majordomo2 install problem. References: <378CC040.5E42E4E2@apple.com> <378CDBCC.66E143EF@apple.com> From: Jason L Tibbitts III Date: 14 Jul 1999 14:50:40 -0500 In-Reply-To: Larry Goodwin's message of "Wed, 14 Jul 1999 11:49:47 -0700" Message-ID: Lines: 25 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "LG" == Larry Goodwin writes: LG> Jason, Thanks for the info. I changed the answer to the question of LG> "where the lists directory should be" to the full path and it worked. OK, I'll add some code to ensure that full paths are given. LG> We would like to stay with MajorCool for the web since everyone is LG> familiar with it. It will be interesting to see how we will have to LG> change it. Given that all of the internals are completely different (100%, no code duplication), MajorCool doesn't have a chance of working in its present state with changes that could be considered to be minor. It should actually be rather easy to get some MajorCool-like software up and running because Mj2 is itself just a library of mailing list management functions. The various interfaces just allocate a Majordomo object and call those routines so it's not necessary to go through the contortions that MajorCool has to deal with. Unfortunately I haven't the time to work on it myself; this would be a great place for others to help out. - J< From majordomo-workers-owner Wed Jul 14 16:49:10 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA13565; Wed, 14 Jul 1999 16:42:40 -0700 (PDT) Received: from sage.coe.uga.edu (sage.coe.uga.edu [128.192.22.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA13558 for ; Wed, 14 Jul 1999 16:42:35 -0700 (PDT) Received: (from pkeck@localhost) by sage.coe.uga.edu (8.9.1/8.9.1) id TAA27897 for majordomo-workers@GreatCircle.COM; Wed, 14 Jul 1999 19:46:10 -0400 (EDT) Date: Wed, 14 Jul 1999 19:46:10 -0400 From: Paul Keck To: majordomo-workers@GreatCircle.COM Subject: Re: Deleting lists Message-ID: <19990714194610.A27188@coe.uga.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jason L Tibbitts III on Wed, Jul 14, 1999 at 10:03:38AM -0500 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk If a lurker and MJ 1.9.x admin could chime in on this list removal issue- I wrote an embarrassingly trivial "rmlist" perl script which copies all the target list info, archives, etc. into a RemovedLists directory. I like the idea of not irrevocably deleting the list, since everyone makes mistakes on occasion and it would be pretty annoying for a list admin to email, "Okay, ready for you to delete my list elan6510!", have me do it, and then they email back, "No wait, I meant elan6501!" Oops! Guess I'll have to set it up from scratch again, and have them resubscribe everyone, if they know who everyone is. My vote, if I get one, is for a "move to temp area" sort of rmlist, and an unrmlist which could bring a list back from the brink. And maybe a "purge" sort of command to get rid of removed lists after a while. Or make everyone do it with a cron "find" command. :-) The important subroutine from my crummy script, if I'm not being clear: sub removeit { my $oldl = shift (@_); my $ripdir = "$removedlistsdir/$oldl"; #rest in peace mkdir $ripdir, 0700; mkdir "$ripdir/Archives", 0700; rename $oldl, "$ripdir/$oldl"; rename "$oldl.config", "$ripdir/$oldl.config"; rename "$oldl.info", "$ripdir/$oldl.info"; rename "$oldl.passwd", "$ripdir/$oldl.passwd"; rename "$oldl.intro", "$ripdir/$oldl.intro"; rename "$oldl.old.config", "$ripdir/$oldl.old.config"; #fix archive files now rename "$filedir/$oldl", "$ripdir/Archives/$oldl"; print "Removed $oldl. It now resides in $ripdir\n"; } Just move the damn things over. (I do the /etc/aliases by hand. Told you it was crummy!) I haven't been on this list long enough to see if there is a "rename list" in the works- I wrote a crummy script for that too. :-) Very handy, since I was always forgetting to rename SOMETHING and MJ would hate me for it. My $.02- keep up the good work! Maybe someday soon I will set up MJ2 on a test box and make some REAL contribution, rather than just pester you hard-working types. -- Paul Keck pkeck@coe.uga.edu http://www.coe.uga.edu/~pkeck Univ. of Georgia- College of Education ftp://ftp.coe.uga.edu/users/pkeck Office of Information Technology (OIT) mailto:pkeck@ediacara.org --Opinions mine, not OIT's.-- Go fighting anomalocaridids!!! From majordomo-workers-owner Thu Jul 15 05:40:50 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA24611; Thu, 15 Jul 1999 05:27:53 -0700 (PDT) Received: from relay.ost.eltele.no (relay.ost.eltele.no [195.70.164.132]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA24604 for ; Thu, 15 Jul 1999 05:27:46 -0700 (PDT) Received: from ws2288 (pc2042.ost.eltele.no) by relay.ost.eltele.no (8.9.3/8.9.3) with ESMTP id OAA18756 for ; Thu, 15 Jul 1999 14:31:23 +0200 (MET DST) Message-ID: <015501becebd$b6afade0$2a021dac@ws2288.ost.eltele.no> Reply-To: "St - Musaic.Net" From: "St - Musaic.Net" To: "Mojo Domo Workers" Subject: HTML and attachments Date: Thu, 15 Jul 1999 14:29:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk ICBUaGlzIGlzIG15IGN1cnJlbnQgVEFCT09fSEVBREVSIHNlY3Rpb246DQoNCj4gL15Db250ZW50 XC1UeXBlXDpccyttdWx0aXBhcnQvaQ0KPiAvXkNvbnRlbnRcLVR5cGVcOlxzK2FwcGxpY2F0aW9u L2kNCj4gL15Db250ZW50XC1UeXBlXDpccyt0ZXh0XC9odG1sL2kNCj4gL15YXC1NU1wtQXR0YWNo bWVudFw6XHMrV0lOTUFJTC5EQVQvaQ0KPiAvXkNvbnRlbnRcLURpc3Bvc2l0aW9uXDpccythdHRh Y2htZW50L2kNCj4gL15Db250ZW50XC1UcmFuc2ZlclwtRW5jb2RpbmdcOlxzK2Jhc2U2NC9pDQo+ IC9eQ29udGVudFwtVHJhbnNmZXJcLUVuY29kaW5nXDpccytxdW90ZWRcLXByaW50YWJsZS9pDQoN CiAgSXQgd29ya3MgYXMgZXhwZWN0ZWQgYW5kIGtlZXBzIHRoZSBsaXN0IGZyb20gYmVpbmcgc3Bh bW1lZA0KICB3aXRoIEhUTUwgYW5kIGF0dGFjaG1lbnRzLg0KDQogIFRoZW4gSSB3YXMgd29uZGVy aW5nOg0KDQogIFdpbGwgTUoyIGJlIGFibGUgdG8gc3RyaXAgdGhlIEhUTUwgY29kZSBmcm9tIGEg bWVzc2FnZSBzbyBvbmx5DQogIHRoZSB0ZXh0LW9ubHkgY291bnRlcnBhcnQgaXMgc2VudCB0byBh IGxpc3Q/IEFuZCB3b3VsZG4ndCBpdCBiZQ0KICBuaWNlIGlmIE1KMiBhbHNvIGNvdWxkIHJlbW92 ZSBhdHRhY2htZW50cyBhdXRvbWF0aWNhbGx5Pw0KDQovIFN0DQoNCg0KDQoNCg== From majordomo-workers-owner Thu Jul 15 21:21:07 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA03680; Thu, 15 Jul 1999 21:03:08 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA03670 for majordomo-workers@greatcircle.com; Thu, 15 Jul 1999 21:03:06 -0700 (PDT) Received: from mirage.texasmicro.com (mirage.texmicro.com [204.95.137.64]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA21253 for ; Tue, 13 Jul 1999 10:55:02 -0700 (PDT) Received: (from scott@localhost) by mirage.texasmicro.com (8.8.6/8.8.6) id MAA05350; Tue, 13 Jul 1999 12:58:09 -0500 Date: Tue, 13 Jul 1999 12:58:09 -0500 From: steve swenson Message-Id: <199907131758.MAA05350@mirage.texasmicro.com> To: tibbs@math.uh.edu Cc: majordomo-workers@greatcircle.com Reply-To: steves@texasmicro.com Subject: Re: From Headers In-Reply-To: X-Mailer: XCmail 0.99.7 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-MS-Mail-Priority: high X-Priority: 1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk ---Reply to mail from Jason L Tibbitts III about From Headers > > I don't think a whole new command is warranted when this is just another > user setting. Plus any address argument would have to be in the form of a > legal RFC822 address. You cannot independently set a comment on an > address, as comments come in many forms and can appear in various places in > the address. > > - J< > Hrm ...maybe I'm confused. I was thinking I could make From: "William M. Wilson" into From: "SSGT Wilson" If the comment field isn't in this format couldn't we have Majordomo convert it... essentially with the user flag set we'd dump whatever comments were already in their FRom: field in favor of one on the list (either pre-set or user configurable depending on List access settings.) ---End reply -- +++++++++++++++ +++++++++++++++ Steven Swenson ### +++++++ ### Technical Support Specialist #### +++++ #### Texas Micro Inc. ##### +++ ##### (800) 627-8700/(713) 541-8200 x110 ###### + ###### (713) 541-8259 FAX ####### ####### steves@texasmicro.com ####### ####### scott@mirage.texmicro.com From majordomo-workers-owner Thu Jul 15 21:36:09 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA03871; Thu, 15 Jul 1999 21:06:04 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA03861 for majordomo-workers@greatcircle.com; Thu, 15 Jul 1999 21:06:02 -0700 (PDT) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA09110 for ; Wed, 14 Jul 1999 09:48:54 -0700 (PDT) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id JAA53676 for ; Wed, 14 Jul 1999 09:52:27 -0700 Received: from scv4.apple.com (scv4.apple.com) by mailgate2.apple.com (mailgate2.apple.com- SMTPRS 2.0.15) with ESMTP id ; Wed, 14 Jul 1999 09:52:18 -0700 Received: from apple.com (shortline.apple.com [17.203.15.65]) by scv4.apple.com (8.9.3/8.9.3) with ESMTP id JAA42292; Wed, 14 Jul 1999 09:52:16 -0700 Message-Id: <378CC040.5E42E4E2@apple.com> Date: Wed, 14 Jul 1999 09:52:16 -0700 From: Larry Goodwin Reply-To: goodwin@apple.com Organization: Apple Computer X-Mailer: Mozilla 4.6 (Macintosh; U; PPC) MIME-Version: 1.0 To: majordomo-workers@greatcircle.com Cc: tibbs@math.uh.edu Subject: majordomo2 install problem. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Folks, I am installing Majordomo2 release "majordomo-0.1199906210" on AIX 4.1.5 and get to make install and get these errors. make and make test were successful. Any ideas. What is the default global password for domain blueske? ->majordomo Setting configuration defaults for blueske:..................................... ................................................................................ .........................................................................ok. Can't find site config file blueske/SITE/config.pl: No such file or directory at /usr/local/majordomo2/lib/Mj/Log.pm line 402 Log::In::abort('Log::In=HASH(0x2030c12c)', 'Can\'t find site config file blueske/SITE/config.pl: No such fil...') called at /usr/local/majordomo2/lib/Ma jordomo.pm line 146 Majordomo::new('Majordomo', 'blueske', 'blueske', 1) called at /usr/loca l/majordomo2/bin/.mj_shell line 146 Error executing /usr/local/majordomo2/bin/mj_shell, 65280 at setup/mta_sendmail. pl line 73. make: *** [postinstall] Error 2 Thanks, -- Larry Goodwin Phone: 408 974-0520 Apple Computer Fax: 408 974-0800 1 Infinite Loop Pager: 408 999-8267 Cupertino, CA From majordomo-workers-owner Thu Jul 15 21:50:48 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA03886; Thu, 15 Jul 1999 21:06:11 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA03876 for majordomo-workers@greatcircle.com; Thu, 15 Jul 1999 21:06:09 -0700 (PDT) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA10513 for ; Wed, 14 Jul 1999 11:46:18 -0700 (PDT) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id LAA13452 for ; Wed, 14 Jul 1999 11:49:52 -0700 Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id ; Wed, 14 Jul 1999 11:49:50 -0700 Received: from apple.com (shortline.apple.com [17.203.15.65]) by scv2.apple.com (8.9.3/8.9.3) with ESMTP id LAA11516; Wed, 14 Jul 1999 11:49:48 -0700 Message-Id: <378CDBCC.66E143EF@apple.com> Date: Wed, 14 Jul 1999 11:49:47 -0700 From: Larry Goodwin Reply-To: goodwin@apple.com Organization: Apple Computer X-Mailer: Mozilla 4.6 (Macintosh; U; PPC) MIME-Version: 1.0 To: Jason L Tibbitts III Cc: majordomo-workers@greatcircle.com Subject: Re: majordomo2 install problem. References: <378CC040.5E42E4E2@apple.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Jason, Thanks for the info. I changed the answer to the question of "where the lists directory should be" to the full path and it worked. I was answering blueske.lists and I changed it to /usr/local/majordomo2/blueske.lists Now I can try it out. FYI. We have been using Majordomo 1.94 and MajorCool for about a year now and it works fine except for html coded email sent out of digests. We would like to stay with MajorCool for the web since everyone is familiar with it. It will be interesting to see how we will have to change it. Also I think I will try using cvs for the source to keep up on the latest changes. Thanks again for the quick response. Larry Jason L Tibbitts III wrote: > > >>>>> "LG" == Larry Goodwin writes: > > LG> I am installing Majordomo2 release "majordomo-0.1199906210" on > LG> AIX 4.1.5 and get to make install and get these errors. > > Hmmm. I don't know that anyone's run it on AIX before, though I don't > think that there would be problems. > > LG> Can't find site config file blueske/SITE/config.pl: No such file or > LG> directory > > That's the problem; now, tell us somethig about this file. Does it exist? > What are its permissions? It looks odd that it isn't an absolute path; did > you not supply absolute paths to any of the configuration questions? > > - J< -- Larry Goodwin Phone: 408 974-0520 Apple Computer Fax: 408 974-0800 1 Infinite Loop Pager: 408 999-8267 Cupertino, CA From majordomo-workers-owner Thu Jul 15 22:05:47 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA03628; Thu, 15 Jul 1999 21:02:18 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA03618 for majordomo-workers@greatcircle.com; Thu, 15 Jul 1999 21:02:15 -0700 (PDT) Received: from mirage.texasmicro.com (mirage.texmicro.com [204.95.137.64]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA20586 for ; Tue, 13 Jul 1999 09:41:43 -0700 (PDT) Received: (from scott@localhost) by mirage.texasmicro.com (8.8.6/8.8.6) id LAA05253; Tue, 13 Jul 1999 11:44:51 -0500 Date: Tue, 13 Jul 1999 11:44:51 -0500 From: steve swenson Message-Id: <199907131644.LAA05253@mirage.texasmicro.com> To: tibbs@hpc.uh.edu Cc: majordomo-workers@greatcircle.com Reply-To: steves@texasmicro.com Subject: Re: From Headers In-Reply-To: X-Mailer: XCmail 0.99.7 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-MS-Mail-Priority: high X-Priority: 1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk ---Reply to mail from tibbs@hpc.uh.edu about From Headers > Far enough along that it supports all of the functionality of Majordomo1. > Not far enough along that it can be released as finished. > > ss> Can I run both Majordomo 1 and 2 together on the same machine? > I need to think further about how to implement what you're asking for, but > I can see several possible methods: > > 1) A per-list config, all From: addresses belonging to members are > rewritten to the full address that they joined with. > 2) A per-user setting, doing the same. > > 3) A per-user setting; users can choose exactly the address they want their > From: rewritten to. > > I'll axe #1 now as too coarse-grained. #2 is easy for me to implement and > probably suits your needs. #3 opens up some interesting possibilities. It > is marginally more difficult for me to implement (since there needs to be > an interface for setting the rewritten address) but it shouldn't be too > bad. Ideas? > > I should probably be doing this on majordomo-workers, but what the heck. > Be sure to direct followups appropriately if discussing details. > > - J< Maybe a title command? Have it check and see if the user is a member of the given list. Also Might have the use of the command have restricted access and available to third party. For example only the Personnel office(if so designated) could change titles. Other lists might allow open use of the command for use as "handles". Kinda like your Open, List Restricted options for Majordomo1. title listname useraddress Comment_for_From_Header What do you think? I was Thinking of using a piped Perl program in front of the list to perform your implementation model #1 ... it sounds trivial enough and would suit my needs right now. However, in the future when I appoint list admins it would be pretty clumsy to re-write. ---End reply -- +++++++++++++++ +++++++++++++++ Steven Swenson ### +++++++ ### Technical Support Specialist #### +++++ #### Texas Micro Inc. ##### +++ ##### (800) 627-8700/(713) 541-8200 x110 ###### + ###### (713) 541-8259 FAX ####### ####### steves@texasmicro.com ####### ####### scott@mirage.texmicro.com From majordomo-workers-owner Thu Jul 15 22:20:53 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA03711; Thu, 15 Jul 1999 21:03:34 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA03701 for majordomo-workers@greatcircle.com; Thu, 15 Jul 1999 21:03:32 -0700 (PDT) Received: from mirage.texasmicro.com (mirage.texmicro.com [204.95.137.64]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA24519 for ; Tue, 13 Jul 1999 14:27:11 -0700 (PDT) Received: (from scott@localhost) by mirage.texasmicro.com (8.8.6/8.8.6) id QAA05589; Tue, 13 Jul 1999 16:30:26 -0500 Date: Tue, 13 Jul 1999 16:30:26 -0500 From: steve swenson Message-Id: <199907132130.QAA05589@mirage.texasmicro.com> To: tibbs@math.uh.edu Cc: majordomo-workers@greatcircle.com Reply-To: steves@texasmicro.com Subject: Re: From Headers In-Reply-To: X-Mailer: XCmail 0.99.7 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-MS-Mail-Priority: high X-Priority: 1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk ---Reply to mail from Jason L Tibbitts III about From Headers >>>>>> "ss" == steve swenson writes: > > ss> If the comment field isn't in this format couldn't we have Majordomo > ss> convert it... > > Here is a legal RFC822 address which Majordomo understands and can deal > with just fine: > > Jason (tibbs) Tibbitts (Me) > > Please tell me how to convert it. I don't think you want it turned into: > > Jason tibbs Tibbitts da man ematics Me For my purposes that would work except I'd dump everything except the actual address which I'd use to reference the membership list and see if you (or the list admin) had referenced a comment. If so then I would rewrite the header as From:"Comment" if not I'd leave the existing comments in the header. So if in the list your entry was A Majordomo Author All mail you sent going through the list from that address would be Identified as coming from "A Majordomo Author" rather than from Jason tibbs Tibbitts da man ematics Me that your mailer supplied. In most cases the user, list-owner, and majordomo owner would be able to modify the replacement comment. This access should be configurable. So I guess to sum it up: 1. Identify emailaddress user@somehost 2. Does user@somehost have a comment in members list? 3a. If yes then rewrite from Header to "comment" 3b. If no then leave From Header alone. I hope that more clearly explains what I was wanting to do, I did d/l RFC 822... I'll give it a read tonight. --Steve > These things are not easy. If what was a simple feature request turns into > a mess of special cases and bizarre requirements I'll drop it rather > quickly. > > As it stands, it's one of: > > User sets a flag and when Majordomo sees their From: address it is > rewritten into the form they supplied when they joined. > > or > > User chooses a legal (though not necessarily deliverable) RFC822 address; > when Majordomo sees their From: address it is rewritten. > > Note that these two options were chosen because they're easy to implement > (the first is around ten lines) and simple to understand. When you get > into converting addresses into different forms, just modifying the > comments, and other such things then it's not simple even before you > consider that RFC822 lets users do some very disgusting things that _must_ > be supported. > > Note also that there will eventually be functionality to change the address > that you are subscribed as; that is completely orthogonal from the current > discussion. > > - J< ---End reply -- +++++++++++++++ +++++++++++++++ Steven Swenson ### +++++++ ### Technical Support Specialist #### +++++ #### Texas Micro Inc. ##### +++ ##### (800) 627-8700/(713) 541-8200 x110 ###### + ###### (713) 541-8259 FAX ####### ####### steves@texasmicro.com ####### ####### scott@mirage.texmicro.com From majordomo-workers-owner Sat Jul 17 15:20:30 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA01552; Sat, 17 Jul 1999 15:04:26 -0700 (PDT) Received: from mail.dnt.ro (ns.dnt.ro [193.226.100.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA01544 for ; Sat, 17 Jul 1999 15:04:18 -0700 (PDT) Received: from DNT.RO (mescalito.dnt.ro [193.226.100.55]) by mail.dnt.ro (8.9.3/8.9.3) with ESMTP id BAA19478; Sun, 18 Jul 1999 01:02:27 +0300 Message-ID: <3790FF2B.9CFEA83D@DNT.RO> Date: Sun, 18 Jul 1999 01:09:47 +0300 From: Stefanita Vilcu Organization: Dynamic Network Technologies, Bucuresti X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-workers@greatcircle.com CC: tibbs@math.uh.edu Subject: Mj2: I need case insesitive addresses Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hello, I am trying to convert my lists from listserv to majordomo2. My problem is that listserv stores the subscriber's address in uppercase. How can I make majordomo 2 to be case insensitive with the usernames? TIA Stefanita -- Stefanita Valeriu Vilcu, vsv@dnt.ro Dynamic Network Technologies Bucuresti, Romania Tel: +40-1-2106863 Fax: +40-1-3122745 From majordomo-workers-owner Sat Jul 17 15:34:14 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA01674; Sat, 17 Jul 1999 15:24:02 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA01667 for ; Sat, 17 Jul 1999 15:23:57 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id RAA26476; Sat, 17 Jul 1999 17:27:14 -0500 To: Stefanita Vilcu Cc: majordomo-workers@greatcircle.com Subject: Re: Mj2: I need case insesitive addresses References: <3790FF2B.9CFEA83D@DNT.RO> From: Jason L Tibbitts III Date: 17 Jul 1999 17:27:14 -0500 In-Reply-To: Stefanita Vilcu's message of "Sun, 18 Jul 1999 01:09:47 +0300" Message-ID: Lines: 23 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "SV" == Stefanita Vilcu writes: SV> How can I make majordomo 2 to be case insensitive with the usernames? Look at the addr_xforms variable. I think this will work for you: configset GLOBAL addr_xforms <; Sun, 18 Jul 1999 13:08:09 -0700 (PDT) Received: from mipczota (200.33.246.70) by intranet.com.mx with SMTP (Eudora Internet Mail Server 2.2); Sun, 18 Jul 1999 15:13:43 -0500 Message-Id: <3.0.6.32.19990718151152.008ecae0@intranet.com.mx> X-Sender: jbiquez@intranet.com.mx X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 18 Jul 1999 15:11:52 +0000 To: Stefanita Vilcu From: Jorge Biquez Subject: Re: Mj2: I need case insesitive addresses Cc: majordomo-workers@greatcircle.com In-Reply-To: <3790FF2B.9CFEA83D@DNT.RO> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hello. I'm sorry to ask , new on majordomo but studying and doing research. Do you know of a URL or document/book that points the difference between MAJORDOMO and LISTSERV? Thanks in advance. At 01:09 AM 18/07/99 +0300, you wrote: >Hello, > >I am trying to convert my lists from listserv to majordomo2. My problem >is that listserv stores the subscriber's address in uppercase. How can >I make majordomo 2 to be case insensitive with the usernames? > >TIA > >Stefanita >-- >Stefanita Valeriu Vilcu, vsv@dnt.ro >Dynamic Network Technologies Bucuresti, Romania >Tel: +40-1-2106863 Fax: +40-1-3122745 > From majordomo-workers-owner Sun Jul 18 13:34:30 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA13626; Sun, 18 Jul 1999 13:15:14 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA13617 for ; Sun, 18 Jul 1999 13:15:08 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id PAA07004; Sun, 18 Jul 1999 15:18:45 -0500 To: majordomo-workers@greatcircle.com Subject: A note on databases From: Jason L Tibbitts III Date: 18 Jul 1999 15:18:44 -0500 Message-ID: Lines: 16 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I recently implemented databases using DB_File. The results are impressive. Running the test from the t/ directory with 1000 entries took ~480 seconds with text files and ~5.8 seconds using DB on my PII-266 at home. In the real world, doing the lookups needed for duplicate removal on my slow test platform took about 3.5 seconds each (there are three done per message) while after the conversion to DB files they're taking from .04 to .11 seconds each. And we get sorting done for free. (The sorting is done such that like domains cluster together for better SMTP performance under Sendmail.) This work is currently in CVS; you can still fall back to the flat text files if you like but the performance is so terrible that I wouldn't recommend it. A tool for converting your existing databases is also provided. Be sure to read README.UPGRADE as usual. - J< From majordomo-workers-owner Sun Jul 18 23:02:55 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA18747; Sun, 18 Jul 1999 22:43:57 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id WAA18737 for majordomo-workers@greatcircle.com; Sun, 18 Jul 1999 22:43:49 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA26025 for ; Thu, 15 Jul 1999 07:57:27 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA08377; Thu, 15 Jul 1999 10:00:41 -0500 To: majordomo-workers@greatcircle.com, "St - Musaic.Net" Subject: Re: HTML and attachments References: <015501becebd$b6afade0$2a021dac@ws2288.ost.eltele.no> From: Jason L Tibbitts III Date: 15 Jul 1999 10:00:40 -0500 In-Reply-To: "St - Musaic.Net"'s message of "Thu, 15 Jul 1999 14:29:25 +0200" Message-ID: Lines: 16 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "St" == "St <- Musaic.Net" > writes: St> Will MJ2 be able to strip the HTML code from a message so only the St> text-only counterpart is sent to a list? No, it doesn't currently do this. A good portion of the infrastructure is there but nobody's written the code. St> And wouldn't it be nice if MJ2 also could remove attachments St> automatically? Yes, wouldn't it be nice? People are going to have to contribute if they want this kind of thing. I'd like it to be there myself, but don't have the time to do it. - J< From majordomo-workers-owner Sun Jul 18 23:13:44 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA18781; Sun, 18 Jul 1999 22:44:42 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id WAA18771 for majordomo-workers@greatcircle.com; Sun, 18 Jul 1999 22:44:40 -0700 (PDT) Received: from mirage.texasmicro.com (mirage.texmicro.com [204.95.137.64]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA12907; Fri, 16 Jul 1999 07:28:21 -0700 (PDT) Received: (from scott@localhost) by mirage.texasmicro.com (8.8.6/8.8.6) id JAA17491; Fri, 16 Jul 1999 09:31:51 -0500 Date: Fri, 16 Jul 1999 09:31:51 -0500 From: steve swenson Message-Id: <199907161431.JAA17491@mirage.texasmicro.com> To: tibbs@math.uh.edu Cc: eckert@climber.org, majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Reply-To: steves@texasmicro.com Subject: Re: From Headers In-Reply-To: X-Mailer: XCmail 0.99.7 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-MS-Mail-Priority: high X-Priority: 1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I have to agree with Mr. Tibbs here. In my case I have a special list for an organization that it would be beneficial to overide user settings. However as a general option it is probably best left to the user. --Steve ---Reply to mail from Jason L Tibbitts III about From Headers >>>>>> "S" == SRE writes: > > S> OK, I'm just suggesting another place to get the replacement text. I > S> agree the "From:" header should be the first choice, but we're talking > S> about alternatives... > > The point I was trying to make was that things like From: shouldn't be > rewritten unless the list is somehow "special" or the user has requested > it. > > S> If you're allowing the "From:" header to be replaced, one possible > S> option is to let the user store new text. > > That's #3 in my previous messages. > > S> Another possible option is to use the global registry. > > Why the global database? This is most definitely a per-list setting. For > instance, I might want to change my address to > > Jason Tibbitts (Moderator) > > for lists that I moderate. (Of course, my mail software lets me do that > already, but few do.) > > - J< > ---End reply -- +++++++++++++++ +++++++++++++++ Steven Swenson ### +++++++ ### Technical Support Specialist #### +++++ #### Texas Micro Inc. ##### +++ ##### (800) 627-8700/(713) 541-8200 x110 ###### + ###### (713) 541-8259 FAX ####### ####### steves@texasmicro.com ####### ####### scott@mirage.texmicro.com From majordomo-workers-owner Mon Jul 19 10:36:58 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28396; Mon, 19 Jul 1999 10:25:03 -0700 (PDT) Received: from milam.acstaff.uwosh.edu (milam.acstaff.uwosh.edu [141.233.129.180]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id KAA28385 for ; Mon, 19 Jul 1999 10:24:56 -0700 (PDT) Received: (qmail 10146 invoked from network); 19 Jul 1999 17:29:22 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 19 Jul 1999 17:29:22 -0000 Date: Mon, 19 Jul 1999 12:29:22 -0500 (CDT) From: Chuck Milam X-Sender: milam@milam.acstaff.uwosh.edu To: majordomo-workers@greatcircle.com cc: Jason L III Tibbitts Subject: Converting from Majordomo 1.9x Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I'm converting a site from Majordomo 1.9x to Majordomo 2. The MJ2 README is quite clear about how to use the mj_shell to create lists and add subscribers from the old list files, but I'm stumped by the next step: "If you copy the old configuration file into the directory for the new list, it will be automatically created." This is ambiguous. What does "it" refer to? If I copy the old configuration file into the directory for the new list, will a new list be created? Or will a new list configuration be created? -- Chuck Milam - milam@uwosh.edu I.T. Division - Academic Computing University of Wisconsin Oshkosh From majordomo-workers-owner Mon Jul 19 10:52:00 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28521; Mon, 19 Jul 1999 10:39:45 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA28514 for ; Mon, 19 Jul 1999 10:39:40 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id MAA20317; Mon, 19 Jul 1999 12:43:26 -0500 To: Chuck Milam Cc: majordomo-workers@greatcircle.com Subject: Re: Converting from Majordomo 1.9x References: From: Jason L Tibbitts III Date: 19 Jul 1999 12:43:25 -0500 In-Reply-To: Chuck Milam's message of "Mon, 19 Jul 1999 12:29:22 -0500 (CDT)" Message-ID: Lines: 16 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "CM" == Chuck Milam writes: CM> "If you copy the old configuration file into the directory for the new CM> list, it will be automatically created." Ugh. The idea is that Mj2 can read old config files and convert them to the new format automatically. This support was put in _long_ ago in the days when I wasn't certain that I wanted to break file-level compatibility with Mj1. While it should still be working, it's probably not the best way to go and there's definitely room for a separate tool to do the conversion. So that code (and documentation bits relating to it) really should be regarded as vestigial. It shouldn't take me too long to cook up an autoconversion tool given that the code is already written. - J< From majordomo-workers-owner Tue Jul 20 06:11:07 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA11601; Tue, 20 Jul 1999 05:56:41 -0700 (PDT) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA11594 for ; Tue, 20 Jul 1999 05:56:34 -0700 (PDT) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by plab.ku.dk (8.9.1/8.9.1) with ESMTP id PAA16695 for ; Tue, 20 Jul 1999 15:01:07 +0200 (CEST) Received: (from tobez@localhost) by lion.plab.ku.dk (8.9.3/8.9.3) id OAA62390 for majordomo-workers@greatcircle.com; Tue, 20 Jul 1999 14:58:48 +0200 (CEST) (envelope-from tobez) Date: Tue, 20 Jul 1999 14:58:48 +0200 From: Anton Berezin To: majordomo-workers@greatcircle.com Subject: mj_shell extension: a proposal+a patch Message-ID: <19990720145848.A61311@lion.plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hello, First, I apologize if this subject was discussed before: I am new on this list. I find mj_shell interface to be a very convenient way to manage lists. Sometimes, however, the output produced by different commands is quite long, so that it even does not fit into a typical xterm history buffer. This is definitely a problem which E-mail interface does not have. I propose to introduce into mj_shell the ability to pipe mj_shell's own output through arbitrary programs, so one should be able to write, for example: Majordomo>help set | more Majordomo>help whatever | /usr/local/bin/less Majordomo>configshow list ALL | grep -v "^#" | grep -v "^$" | more and even Majordomo> | date I am aware of possible security problems with this. I think that normally only trusted people are able to run mj_shell anyway, so this should not be a problem. If I am wrong, please correct me, I would really like to discuss ways to make this more secure, since the feature seems to be very useful (at least for myself :-). I've implemented this with the most recent version of mj_shell. The patch follows: --- /home/tobez/src/majordomo/bin/mj_shell.orig Tue Jul 20 14:17:21 1999 +++ /home/tobez/src/majordomo/bin/mj_shell Tue Jul 20 14:29:45 1999 @@ -199,10 +199,34 @@ while (defined($cmdline = $term->readline($prompt))) { print "\n"; + + my $cleanup; + $cmdline =~ s/(\|.*)$//; + if ( $1) { + $cleanup = sub { + close STDOUT unless @_; + open STDOUT, ">&OLDOUT"; + close OLDOUT; + $SIG{PIPE} = 'DEFAULT'; + $cleanup = 0; + }; + $SIG{PIPE} = 'IGNORE'; + open OLDOUT, ">&STDOUT"; + local $SIG{__WARN__} = sub { + my $s = $_[0]; + $s =~ s/ at .* line \d+//; + print STDERR "--== $s"; + }; + $cleanup->("do not close!") unless open STDOUT, $1; + } + ($cmd, $args) = $cmdline =~ /(\S*)\s*(.*)/; if ($cmd) { ($go, $res) = parse_command($cmd, $args, $pass); + $cleanup->() if $cleanup; return 1 unless $go; + } else { + $cleanup->() if $cleanup; } print "\n"; } -- Anton Berezin The Protein Laboratory, University of Copenhagen From majordomo-workers-owner Tue Jul 20 09:58:46 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA13853; Tue, 20 Jul 1999 09:41:20 -0700 (PDT) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA13846 for ; Tue, 20 Jul 1999 09:41:14 -0700 (PDT) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by plab.ku.dk (8.9.1/8.9.1) with ESMTP id SAA18437 for ; Tue, 20 Jul 1999 18:45:49 +0200 (CEST) Received: (from tobez@localhost) by lion.plab.ku.dk (8.9.3/8.9.3) id SAA63485 for majordomo-workers@GreatCircle.COM; Tue, 20 Jul 1999 18:43:31 +0200 (CEST) (envelope-from tobez) Date: Tue, 20 Jul 1999 18:43:31 +0200 From: Anton Berezin To: majordomo-workers@GreatCircle.COM Subject: mj_shell completer bug (+patch) Message-ID: <19990720184331.A63459@lion.plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hello, There is a bug in completer() sub in mj_shell. If you try to complete something like 'aa[', for example, mj_shell will die since completer does not quote appropriate parts in the regexes it uses. This patch solves this: --- /home/tobez/src/majordomo/bin/mj_shell.orig Tue Jul 20 14:17:21 1999 +++ /home/tobez/src/majordomo/bin/mj_shell Tue Jul 20 18:39:22 1999 @@ -379,7 +379,7 @@ # on in the string. # At the beginning, any command will do if ($pos == 0) { - @out = commands_matching("^$word", $ac, ['shell']); + @out = commands_matching("^\Q$word\E", $ac, ['shell']); return sort @out; } # If we're completing the password, no completion @@ -393,20 +393,20 @@ } # If now on a command, complete real commands if ($line =~ /^\S*$/) { - @out = commands_matching("^$word", $ac, ['shell', 'real']); + @out = commands_matching("^\Q$word\E", $ac, ['shell', 'real']); return sort @out; } # If on the second word after a command, complete as a list if ($line =~ /^(\S+)\s*(\S*)$/ && command_prop($1, 'list')) { @lists = $mj->get_all_lists($user, $pass, '', 'shell'); - return sort(grep(/^$2/, @lists)); + return sort(grep(/^\Q$2\E/, @lists)); } # Complete config variables. XXX This doesn't handle completion of group # names, but I'm inclined to not worry about it. if ($line =~ /^config\S+\s+(\S+)\s+(\S*)$/) { @vars = $mj->config_get_vars($user, $pass, '', 'shell', $1, 'ALL'); - return sort(grep(/^$2/, @vars)); + return sort(grep(/^\Q$2\E/, @vars)); } (); } Enjoy, -- Anton Berezin The Protein Laboratory, University of Copenhagen From majordomo-workers-owner Tue Jul 20 11:11:59 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA14873; Tue, 20 Jul 1999 11:01:28 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA14866 for ; Tue, 20 Jul 1999 11:01:23 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id NAA04989; Tue, 20 Jul 1999 13:05:13 -0500 To: majordomo-workers@greatcircle.com, Anton Berezin Subject: Re: mj_shell extension: a proposal+a patch References: <19990720145848.A61311@lion.plab.ku.dk> From: Jason L Tibbitts III Date: 20 Jul 1999 13:05:13 -0500 In-Reply-To: Anton Berezin's message of "Tue, 20 Jul 1999 14:58:48 +0200" Message-ID: Lines: 33 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "AB" == Anton Berezin writes: AB> I propose to introduce into mj_shell the ability to pipe mj_shell's own AB> output through arbitrary programs, so one should be able to write, for AB> example: Danger! Danger! AB> I am aware of possible security problems with this. I think that AB> normally only trusted people are able to run mj_shell anyway, so this AB> should not be a problem. No, anyone can run mj_shell (unless you somehow restrict it yourself, but that it not the default configuration). It is a general interface to all Majordomo functionality, including base user stuff like joining lists and such. You've given anyone with the ability to run the command (i.e. everyone in the system) the ability to do anything with your Majordomo setup, including delete it all. Even when running as a "privileged" user (i.e. someone who has a password) we still take pains to secure things because giving someone a limited-use password shouldn't be construed as giving them write access to all of the internal Majordomo files. Look at the UID switching and such within the configedit routine so that the editor runs at the proper user. And while that code seems OK to me (as I copied it from the crontab sources) I'm no security expert. I think it would be useful to respect $PAGER but I think this general piping syntax isn't going to work. And that's completely ignoring the fact that you can't just usurp a perfectly valid character like '|' and give it some special meaning. - J< From majordomo-workers-owner Tue Jul 20 11:26:06 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA15025; Tue, 20 Jul 1999 11:16:45 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA15018 for ; Tue, 20 Jul 1999 11:16:40 -0700 (PDT) Received: from ee-nt (eckert@netcom16.netcom.com [192.100.81.129]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id LAA08851; Tue, 20 Jul 1999 11:21:06 -0700 (PDT) Message-Id: <3.0.5.32.19990720111320.0098a4c0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 20 Jul 1999 11:13:20 -0700 To: tibbs@hpc.uh.edu From: SRE Subject: list names that are too complete (mj2) Cc: majordomo-workers@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Many commands require the user to specify a list name, but it is considered an error if the list is specified as a full email address instead of just the name. For example: set my-list@climber.org nomail eckert@climber.org >Illegal list "my-list@climber.org". >**** Illegal command! >No valid commands processed. Would it be possible to parse the list name field and remove the domain? Or when an "illegal list" is specified, give back a hint suggesting the user send without a domain name (using the address they put down since some don't know what a domain name actually is)? I would like these command to work the same way: set my-list@climber.org nomail eckert@climber.org set my-list nomail eckert@climber.org as long as the request was sent to a server whose domain is climber.org Failing that, I would like the error message to say: Illegal list "my-list@climber.org". Try sending the command "set my-list nomail eckert@climber.org" instead. From majordomo-workers-owner Tue Jul 20 11:57:29 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA15186; Tue, 20 Jul 1999 11:35:16 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA15177 for ; Tue, 20 Jul 1999 11:35:10 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id NAA05653; Tue, 20 Jul 1999 13:39:02 -0500 To: SRE Cc: majordomo-workers@GreatCircle.COM Subject: Re: list names that are too complete (mj2) References: <3.0.5.32.19990720111320.0098a4c0@pop.climber.org> From: Jason L Tibbitts III Date: 20 Jul 1999 13:39:01 -0500 In-Reply-To: SRE's message of "Tue, 20 Jul 1999 11:13:20 -0700" Message-ID: Lines: 11 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "S" == SRE writes: S> Many commands require the user to specify a list name, but it is S> considered an error if the list is specified as a full email address S> instead of just the name. For example: Well, we could just drop everything after the '@' since it can't appear in a listname and it's rather painfully obvious that the user would like that done. I can't imagine any reason why we'd want to keep it around. - J< From majordomo-workers-owner Tue Jul 20 12:10:56 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA15256; Tue, 20 Jul 1999 11:41:02 -0700 (PDT) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA15249 for ; Tue, 20 Jul 1999 11:40:55 -0700 (PDT) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by plab.ku.dk (8.9.1/8.9.1) with ESMTP id UAA19311; Tue, 20 Jul 1999 20:45:30 +0200 (CEST) Received: (from tobez@localhost) by lion.plab.ku.dk (8.9.3/8.9.3) id UAA64951; Tue, 20 Jul 1999 20:43:12 +0200 (CEST) (envelope-from tobez) Date: Tue, 20 Jul 1999 20:43:12 +0200 From: Anton Berezin To: Jason L Tibbitts III Cc: majordomo-workers@greatcircle.com Subject: Re: mj_shell extension: a proposal+a patch Message-ID: <19990720204312.B63674@lion.plab.ku.dk> References: <19990720145848.A61311@lion.plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jason L Tibbitts III on Tue, Jul 20, 1999 at 01:05:13PM -0500 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Tue, Jul 20, 1999 at 01:05:13PM -0500, Jason L Tibbitts III wrote: > >>>>> "AB" == Anton Berezin writes: >> I propose to introduce into mj_shell the ability to pipe mj_shell's >> own output through arbitrary programs, so one should be able to >> write, for example: > > Danger! Danger! Well, after some thought I agree with that. > I think it would be useful to respect $PAGER but I think this general > piping syntax isn't going to work. Alright. It can be done automagically, by tying the STDOUT before the parse_command() call, and untying it afterwards. Then, appropriate PRINT (and PRINTF) subs will accumulate output strings, and as soon as the current terminal height lines are accumulated, will invoke a $PAGER (can we trust a $PAGER, though?). If the limit is not reached, all output lines will be spewed to the real STDOUT during or immediately after the untie operation. This will cause a minor (I hope) delay for short pieces of output text. There is one more problem, though. In order to find a window size, either sys/ioctl.ph, or Term::ReadKey (which, I am afraid, also uses sys/ioctl.ph) should be installed. This adds one more required module/file in order for Mj2 to work. Is it a problem? If that's OK, I can send a patch for this tomorrow. Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen From majordomo-workers-owner Tue Jul 20 12:27:30 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA15591; Tue, 20 Jul 1999 12:05:43 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA15584 for ; Tue, 20 Jul 1999 12:05:38 -0700 (PDT) Received: from ee-nt (eckert@netcom16.netcom.com [192.100.81.129]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id MAA09326; Tue, 20 Jul 1999 12:10:08 -0700 (PDT) Message-Id: <3.0.5.32.19990720121123.0097e6b0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 20 Jul 1999 12:11:23 -0700 To: Jason L Tibbitts III From: SRE Subject: Re: list names that are too complete (mj2) Cc: majordomo-workers@GreatCircle.COM In-Reply-To: References: <3.0.5.32.19990720111320.0098a4c0@pop.climber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 01:39 PM 7/20/99 -0500, Jason L Tibbitts III wrote: >Well, we could just drop everything after the '@' since it can't appear in >a listname and it's rather painfully obvious that the user would like that >done. I can't imagine any reason why we'd want to keep it around. That works for me! I suggested the domain name check only in case someone has forwarded or bounced mail, not because I think it's required. From majordomo-workers-owner Tue Jul 20 12:41:20 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA15843; Tue, 20 Jul 1999 12:27:48 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA15836 for ; Tue, 20 Jul 1999 12:27:42 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id OAA06435; Tue, 20 Jul 1999 14:31:33 -0500 To: majordomo-workers@greatcircle.com, Anton Berezin Subject: Re: mj_shell completer bug (+patch) References: <19990720184331.A63459@lion.plab.ku.dk> From: Jason L Tibbitts III Date: 20 Jul 1999 14:31:33 -0500 In-Reply-To: Anton Berezin's message of "Tue, 20 Jul 1999 18:43:31 +0200" Message-ID: Lines: 7 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "AB" == Anton Berezin writes: AB> Hello, There is a bug in completer() sub in mj_shell. Yep. Patch applied and committed; thanks! - J< From majordomo-workers-owner Tue Jul 20 12:55:46 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA15725; Tue, 20 Jul 1999 12:12:51 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA15718 for ; Tue, 20 Jul 1999 12:12:43 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id OAA06194; Tue, 20 Jul 1999 14:16:36 -0500 To: Anton Berezin Cc: majordomo-workers@greatcircle.com Subject: Re: mj_shell extension: a proposal+a patch References: <19990720145848.A61311@lion.plab.ku.dk> <19990720204312.B63674@lion.plab.ku.dk> From: Jason L Tibbitts III Date: 20 Jul 1999 14:16:35 -0500 In-Reply-To: Anton Berezin's message of "Tue, 20 Jul 1999 20:43:12 +0200" Message-ID: Lines: 37 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "AB" == Anton Berezin writes: AB> It can be done automagically, by tying the STDOUT before the AB> parse_command() call, and untying it afterwards. You don't even have to do that far; note that the call to &{"Mj::TextOutput::$true_command"} takes the output filehandle to use. Nothing in the guts of the code cares about STDOUT, so you can just pass something different. I'd just recommend a tempfile opened (mode 600) as the user. There's already code to do that in there; it should probably be turned into a subroutine: # Switch UIDs, open a file, restore $tmpu = $>; $> = $<; $tmpg = $); $) = $(; $fh = new IO::File "$::WTMPDIR/mjs.$$.AAA", O_WRONLY|O_CREAT, 0600; $> = $tmpu; $) = $tmpg; Heck, if mj_shell's getting some hack time again it would be nice to clean it up (pull things out into subs, remove IO::File dependence, etc.) but that isn't high priority. AB> (can we trust a $PAGER, though?). No. You must run the pager on the temporary file as the user, switching IDs around before and after. It's a pain. AB> There is one more problem, though. In order to find a window size, AB> either sys/ioctl.ph, or Term::ReadKey (which, I am afraid, also uses AB> sys/ioctl.ph) should be installed. I'd prefer not to require these, although using them falling back gracefully is OK. What's wrong with $ENV{LINES}? Not widely supported? Actually, why bother counting lines and such? Why not just always invoke the pager? (According to some command line flag, of course.) - J< From majordomo-workers-owner Tue Jul 20 23:48:01 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id XAA22007; Tue, 20 Jul 1999 23:40:25 -0700 (PDT) Received: from mail.cs.uta.fi (mail.cs.uta.fi [153.1.55.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id XAA21998 for ; Tue, 20 Jul 1999 23:40:19 -0700 (PDT) Received: from [153.1.55.46] (heimonen.cs.uta.fi [153.1.55.46]) by mail.cs.uta.fi (8.9.2/8.9.2) with ESMTP id JAA11345 for ; Wed, 21 Jul 1999 09:45:00 +0300 (EEST) X-Sender: jmh@mail.cs.uta.fi Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 21 Jul 1999 09:44:59 +0300 To: majordomo-workers@GreatCircle.com From: Juha-Matti Heimonen Subject: Substitution loop Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk The following substitution statements gave some error message telling about "substitution loop" or something. I tried to repeat the error with a small sample script but i couldn't. In majordomo: s/^\s*//g; # strip leading whitespace s/\s*$//g; # strip trailing whitespace In majordomo.pl: $clean_list =~ s/[^-_0-9a-zA-Z]*//g; Majordomo started to work when I replaced * by + as follows: s/^\s+//g; # strip leading whitespace s/\s+$//g; # strip trailing whitespace and $clean_list =~ s/[^-_0-9a-zA-Z]+//g; Has anyone encountered the same problem? -- jmh _________________________________________________________________ Juha-Matti Heimonen University of Tampere tel: (0)3-2157059 Department of Computer Science fax: (0)3-2156070 P.O. Box 607 (Kehruukoulunkatu 1) e-mail: jmh@cs.uta.fi 33101 Tampere, FINLAND From majordomo-workers-owner Wed Jul 21 07:39:45 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA28835; Wed, 21 Jul 1999 07:20:15 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA28826 for ; Wed, 21 Jul 1999 07:20:09 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id JAA19093; Wed, 21 Jul 1999 09:24:07 -0500 To: majordomo-workers@greatcircle.com, Juha-Matti Heimonen Subject: Re: Substitution loop References: From: Jason L Tibbitts III Date: 21 Jul 1999 09:24:07 -0500 In-Reply-To: Juha-Matti Heimonen's message of "Wed, 21 Jul 1999 09:44:59 +0300" Message-ID: Lines: 12 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "JH" == Juha-Matti Heimonen writes: JH> The following substitution statements gave some error message telling JH> about "substitution loop" or something. I tried to repeat the error JH> with a small sample script but i couldn't. You have a broken version of Perl. Since you provided essentially no information, let's guess: you have RedHat 5.2 running what it _says_ is perl 5.004_04 but which is actually a previous development version. If so, please upgrade. - J< From majordomo-workers-owner Wed Jul 21 16:54:27 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA04009; Wed, 21 Jul 1999 16:35:45 -0700 (PDT) Received: from server.postmodern.com (server.postmodern.com [209.157.82.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA03952 for ; Wed, 21 Jul 1999 16:35:24 -0700 (PDT) Received: from scifi.squawk.com (dialup.squawk.com [208.143.248.61]) by server.postmodern.com (8.8.5/mcb-980201) with ESMTP id MAA08481 for ; Wed, 21 Jul 1999 12:24:04 -0700 (PDT) Received: from tpad.squawk.com (localhost [127.0.0.1]) by scifi.squawk.com (8.8.7/8.8.7) with SMTP id PAA10655; Wed, 21 Jul 1999 15:11:50 -0400 Message-Id: <3.0.5.32.19990721124606.03ed6c90@127.0.0.1> X-Sender: njs@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 21 Jul 1999 12:46:06 -0400 To: Juha-Matti Heimonen From: Nick Simicich Subject: Re: Substitution loop Cc: majordomo-workers@greatcircle.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Yes, I have had this problem. Since technically, a phrase like ^\s* can match a zero width point at the beginning/end/where-ever in the string, without special coding it will continue to match there. I think that either the * can be changed to + or 'g' can be removed and that doing both is the best idea, as there is clearly redundancy. However, like you, I can't make it cail in a short script. At 09:44 AM 7/21/99 +0300, Juha-Matti Heimonen wrote: >The following substitution statements gave some error message telling >about "substitution loop" or something. I tried to repeat the error >with a small sample script but i couldn't. > >In majordomo: > s/^\s*//g; # strip leading whitespace > s/\s*$//g; # strip trailing whitespace > >In majordomo.pl: > $clean_list =~ s/[^-_0-9a-zA-Z]*//g; > > >Majordomo started to work when I replaced * by + as follows: > > s/^\s+//g; # strip leading whitespace > s/\s+$//g; # strip trailing whitespace >and > $clean_list =~ s/[^-_0-9a-zA-Z]+//g; > >Has anyone encountered the same problem? > >-- jmh > >_________________________________________________________________ >Juha-Matti Heimonen University of Tampere >tel: (0)3-2157059 Department of Computer Science >fax: (0)3-2156070 P.O. Box 607 (Kehruukoulunkatu 1) >e-mail: jmh@cs.uta.fi 33101 Tampere, FINLAND > > -- That which does not kill us, makes us stronger. That which does kill us makes us smell stronger, after a few days, anyway. Nick Simicich mailto:njs@scifi.squawk.com or (last choice) mailto:njs@us.ibm.com http://scifi.squawk.com/njs.html -- Stop by and Light Up The World! From majordomo-workers-owner Fri Jul 23 06:24:28 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA02647; Fri, 23 Jul 1999 06:03:10 -0700 (PDT) Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.12.23]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id GAA02640 for ; Fri, 23 Jul 1999 06:03:06 -0700 (PDT) Received: (qmail 17078 invoked by uid 50); 23 Jul 1999 13:08:11 -0000 To: Nick Simicich Cc: majordomo-workers@GreatCircle.COM Subject: Re: Substitution loop References: <3.0.5.32.19990721124606.03ed6c90@127.0.0.1> From: Russ Allbery In-Reply-To: Nick Simicich's message of "Wed, 21 Jul 1999 12:46:06 -0400" Date: 23 Jul 1999 06:08:11 -0700 Message-ID: Lines: 15 X-Mailer: Gnus v5.4.66/Emacs 19.34 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Nick Simicich writes: > Yes, I have had this problem. Since technically, a phrase like ^\s* can > match a zero width point at the beginning/end/where-ever in the string, > without special coding it will continue to match there. I think that > either the * can be changed to + or 'g' can be removed and that doing > both is the best idea, as there is clearly redundancy. Non-broken versions of Perl deal with this just fine. Red Hat 5.2 shipped with a broken, unreleased, maintenance-trial version of Perl that didn't. (The Perl maintainers were extremely annoyed at Red Hat for doing that; the version that was released was not suitable for production use.) -- Russ Allbery (rra@stanford.edu) From majordomo-workers-owner Fri Jul 23 11:22:13 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA06312; Fri, 23 Jul 1999 11:07:02 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA06302 for majordomo-workers@greatcircle.com; Fri, 23 Jul 1999 11:07:00 -0700 (PDT) Received: from idefix.icce.rug.nl (idefix.icce.rug.nl [129.125.14.149]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA29861 for ; Wed, 21 Jul 1999 08:40:53 -0700 (PDT) Received: (from piet@localhost) by idefix.icce.rug.nl (8.9.3/8.9.3/Debian/GNU) id RAA03474 for Majordomo-Workers@GreatCircle.com; Wed, 21 Jul 1999 17:45:39 +0200 Received: (from piet@localhost) by idefix.icce.rug.nl (8.9.3/8.9.3/Debian/GNU) id RAA03464; Wed, 21 Jul 1999 17:44:35 +0200 From: "Piet W. Plomp" Message-Id: <199907211544.RAA03464@idefix.icce.rug.nl> Subject: need to restrict resend To: Majordomo_Workers@GreatCircle.com Date: Wed, 21 Jul 1999 17:44:35 +0200 (CEST) Reply-To: piet@idefix.icce.rug.nl X-Mailer: ELM [version 2.4ME+ PL48 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Dear Majordomo workgroup, This is more or less a feature request, that might be useful to the rest of the world. I'm willing to implement it myself first. I get a report of a person who sends up to 1000 messages/day to a X400 system (BICS, mails non-sea ships). Majordomo happily sends these messages to him, which becomes a nuisance. The message characteristic: Subject: X.400 Delivery Report The quickest way to do it is edit the scripts myself (I'm an experienced Perl programmer), so I started looking for a place to intercept the subject. I remember having I edited the code in an earlier version several years ago, trying to intercept the RCPT: confirmation messages sent out by Pegasus mail. A newer version did that automaticaly, so I forgot all about it. When I look in the code now, the only place that contains RCPT: is the sequencer program in the Tools subdirectory. I don't see it being called by any other Majordomo software. System data: Linux Debian 2.1 (slink) w/ perl 5.004 Majordomo 1.94.4 (of course) from the Debian distribution Sendmail 8.9.3 Summary: I'm willing to edit the software to ignore 'X400 delivery report' but cannot find the location. Of course I want to share the solution with you. Thanks for any pointers, -- Piet W. Plomp, Groningen University, NL | --- __ o __~o piet@icce.rug.nl, piet@idefix.icce.rug.nl | ---- _`\<, _`\<, ICCE: +31 50 363 3727; ICT PPSW: +31 50 363 6373 | --- ( )/( ) ( )/( ) fax: (+31)(0)20 882 17 22 (xoip) From majordomo-workers-owner Fri Jul 23 14:52:01 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA08926; Fri, 23 Jul 1999 14:33:12 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA08919 for ; Fri, 23 Jul 1999 14:33:03 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id QAA20876; Fri, 23 Jul 1999 16:37:19 -0500 To: majordomo-workers@greatcircle.com, piet@idefix.icce.rug.nl Subject: Re: need to restrict resend References: <199907211544.RAA03464@idefix.icce.rug.nl> From: Jason L Tibbitts III Date: 23 Jul 1999 16:37:19 -0500 In-Reply-To: "Piet W. Plomp"'s message of "Wed, 21 Jul 1999 17:44:35 +0200 (CEST)" Message-ID: Lines: 11 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "PWP" == Piet W Plomp writes: PWP> This is more or less a feature request, that might be useful to the PWP> rest of the world. I'd like to help you, but I honestly can't tell at all just what it is you're trying to accomplish. Could you try to explain _clearly_ what you want done? - J< From majordomo-workers-owner Fri Jul 23 16:37:39 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA10301; Fri, 23 Jul 1999 16:30:14 -0700 (PDT) Received: from ivan.iecc.com (ivan.iecc.com [208.31.42.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id QAA10292 for ; Fri, 23 Jul 1999 16:30:05 -0700 (PDT) Received: (qmail 14368 invoked by uid 100); 23 Jul 1999 19:35:15 -0400 Date: Fri, 23 Jul 1999 19:35:14 -0400 (EDT) From: John R Levine To: majordomo-workers@greatcircle.com Subject: Re: need to restrict resend Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk > The message characteristic: > > Subject: X.400 Delivery Report Wow, I love X.400. It gives new meaning to the phrase "user friendly". Fortunately, it's easy to reject those, using taboo_headers in the list.config file, no extra hackery needed: taboo_headers << END /Subject:.*X.400 Delivery Report/i END My inclination would be to use procmail to intercept those messages before majordomo gets them and mail them back to the bozo who's sending them in the first place. Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Information Superhighwayman wanna-be, http://iecc.com/johnl, Sewer Commissioner Finger for PGP key, f'print = 3A 5B D0 3F D9 A0 6A A4 2D AC 1E 9E A6 36 A3 47 From majordomo-workers-owner Sat Jul 24 15:19:26 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA24148; Sat, 24 Jul 1999 15:10:04 -0700 (PDT) Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA24136 for ; Sat, 24 Jul 1999 15:09:57 -0700 (PDT) Received: from Default (pool036-max4.ds10-ca-us.dialup.earthlink.net [209.178.7.236]) by snipe.prod.itd.earthlink.net (8.9.3/8.9.3) with SMTP id PAA08615 for ; Sat, 24 Jul 1999 15:15:16 -0700 (PDT) Date: Sat, 24 Jul 1999 15:15:16 -0700 (PDT) Message-Id: <199907242215.PAA08615@snipe.prod.itd.earthlink.net> X-Sender: sbrooks@mail.earthlink.net (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-workers@GreatCircle.COM From: Sam Brooks Subject: BSDI Users List Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Pardon the off topic. Don't know where to turn as I've searched the net and no results. Anybody have url/location of BSDI User's Mailing List TIA Sam sbrooks@earthlink.net From majordomo-workers-owner Sat Jul 24 16:34:29 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA24742; Sat, 24 Jul 1999 16:27:21 -0700 (PDT) Received: from fog.ccsf.cc.ca.us (fog.ccsf.cc.ca.us [147.144.1.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA24735 for ; Sat, 24 Jul 1999 16:27:16 -0700 (PDT) Received: from sol.ccsf.cc.ca.us (sol.ccsf.cc.ca.us [147.144.1.211]) by fog.ccsf.cc.ca.us (8.8.6 (PHNE_17135)/8.8.6) with SMTP id QAA23412; Sat, 24 Jul 1999 16:32:36 -0700 (PDT) Received: from localhost by sol.ccsf.cc.ca.us (SMI-8.6/SMI-SVR4) id QAA16692; Sat, 24 Jul 1999 16:32:35 -0700 Date: Sat, 24 Jul 1999 16:32:35 -0700 (PDT) From: "Joe R. Jah" To: Sam Brooks cc: majordomo-workers@GreatCircle.COM Subject: Re: BSDI Users List In-Reply-To: <199907242215.PAA08615@snipe.prod.itd.earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Sat, 24 Jul 1999, Sam Brooks wrote: > Date: Sat, 24 Jul 1999 15:15:16 -0700 (PDT) > From: Sam Brooks > To: majordomo-workers@GreatCircle.COM > Subject: BSDI Users List > > Pardon the off topic. > Don't know where to turn as I've searched the net > and no results. > > Anybody have url/location of > > BSDI User's Mailing List > > TIA > > Sam > sbrooks@earthlink.net Here is the footer of their list: _________________________________________________________________________ To unsubscribe, send 'unsubscribe' to bsdi-users-request@mailinglists.org Archives of this list can be found at: http://www.nexial.com/mailinglists/ A FAQ can be found at: http://faqs.mailinglists.org/bsdi.cgi _________________________________________________________________________ Joe _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@sol.ccsf.cc.ca.us From majordomo-workers-owner Mon Jul 26 14:04:28 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA23165; Mon, 26 Jul 1999 13:56:47 -0700 (PDT) Received: from queernet.queernet.org (queernet.queernet.org [170.1.118.14]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA23158 for ; Mon, 26 Jul 1999 13:56:43 -0700 (PDT) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.9.0/8.9.1) with ESMTP id OAA20782 for ; Mon, 26 Jul 1999 14:02:23 -0700 (PDT) Date: Mon, 26 Jul 1999 14:02:23 -0700 (PDT) From: "Roger B.A. Klorese" To: majordomo-workers@greatcircle.com Subject: Dash-dash-space-newline? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Does anyone remember where, if anywhere, in the RFCs the use of that specific pattern as signature delimiter is described or prescribed? -- ROGER B.A. KLORESE rogerk@QueerNet.ORG urgent: rogerk-page@QueerNet.ORG PO Box 14309 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick From majordomo-workers-owner Mon Jul 26 16:18:05 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA24603; Mon, 26 Jul 1999 16:10:19 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA24596 for ; Mon, 26 Jul 1999 16:10:12 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id SAA07160; Mon, 26 Jul 1999 18:14:51 -0500 To: majordomo-workers@greatcircle.com Subject: Re: Dash-dash-space-newline? References: From: Jason L Tibbitts III Date: 26 Jul 1999 18:14:51 -0500 In-Reply-To: "Roger B.A. Klorese"'s message of "Mon, 26 Jul 1999 14:02:23 -0700 (PDT)" Message-ID: Lines: 11 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "RBAK" == Roger B A Klorese writes: RBAK> Does anyone remember where, if anywhere, in the RFCs the use of that RBAK> specific pattern as signature delimiter is described or prescribed? I do not believe that it is actually in any RFC (although I'm pretty sure it was in son-of-1036 and will be in whatever USEFOR comes up with). At various times (i.e. to end certain debates) I've tried to find hard evidence of the requirement but never managed to do so. - J< From majordomo-workers-owner Mon Jul 26 16:33:05 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA24773; Mon, 26 Jul 1999 16:30:58 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA24766 for ; Mon, 26 Jul 1999 16:30:53 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id SAA07395; Mon, 26 Jul 1999 18:35:27 -0500 To: "Roger B.A. Klorese" Cc: majordomo-workers@GreatCircle.COM Subject: Re: Dash-dash-space-newline? References: From: Jason L Tibbitts III Date: 26 Jul 1999 18:35:26 -0500 In-Reply-To: "Roger B.A. Klorese"'s message of "Mon, 26 Jul 1999 16:33:20 -0700 (PDT)" Message-ID: Lines: 8 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "RBAK" == Roger B A Klorese writes: RBAK> Yes, I could swear I saw it somewhere back when I looked it up in the RBAK> MJ days, but it's nowhere official to be found. I did find it in the GNKSA: http://www.newsreaders.com/gnksa/. - J< From majordomo-workers-owner Mon Jul 26 16:48:07 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA24731; Mon, 26 Jul 1999 16:27:47 -0700 (PDT) Received: from queernet.queernet.org (queernet.queernet.org [170.1.118.14]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA24724 for ; Mon, 26 Jul 1999 16:27:42 -0700 (PDT) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.9.0/8.9.1) with ESMTP id QAA24178; Mon, 26 Jul 1999 16:33:20 -0700 (PDT) Date: Mon, 26 Jul 1999 16:33:20 -0700 (PDT) From: "Roger B.A. Klorese" To: Jason L Tibbitts III cc: majordomo-workers@GreatCircle.COM Subject: Re: Dash-dash-space-newline? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On 26 Jul 1999, Jason L Tibbitts III wrote: > >>>>> "RBAK" == Roger B A Klorese writes: > > RBAK> Does anyone remember where, if anywhere, in the RFCs the use of that > RBAK> specific pattern as signature delimiter is described or prescribed? > > I do not believe that it is actually in any RFC (although I'm pretty sure > it was in son-of-1036 and will be in whatever USEFOR comes up with). At > various times (i.e. to end certain debates) I've tried to find hard > evidence of the requirement but never managed to do so. Yes, I could swear I saw it somewhere back when I looked it up in the MJ 1.46 days, but it's nowhere official to be found. -- ROGER B.A. KLORESE rogerk@QueerNet.ORG urgent: rogerk-page@QueerNet.ORG PO Box 14309 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick From majordomo-workers-owner Mon Jul 26 17:03:08 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA24939; Mon, 26 Jul 1999 16:52:50 -0700 (PDT) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA24932 for ; Mon, 26 Jul 1999 16:52:42 -0700 (PDT) Received: from lithium.scientia.demon.co.uk ([192.168.1.2] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.02 #1) id 118ubN-0001Ti-00; Tue, 27 Jul 1999 00:56:14 +0100 (envelope-from ben@lithium.scientia.demon.co.uk) Received: from lithium.scientia.demon.co.uk (ident=ben) by lithium.scientia.demon.co.uk with local (Exim 3.02 #1) id 118ubP-00018z-00; Tue, 27 Jul 1999 00:56:15 +0100 (envelope-from ben@lithium.scientia.demon.co.uk) Date: Tue, 27 Jul 1999 00:56:14 +0100 From: Ben Smithurst To: "Roger B.A. Klorese" Cc: majordomo-workers@greatcircle.com Subject: Re: Dash-dash-space-newline? Message-ID: <19990727005614.A4260@lithium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Roger B.A. Klorese wrote: > Does anyone remember where, if anywhere, in the RFCs the use of that > specific pattern as signature delimiter is described or prescribed? I think it's son-of-RFC1036, or something like that, last time I saw it. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk From majordomo-workers-owner Thu Jul 29 07:33:15 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA23067; Thu, 29 Jul 1999 07:30:53 -0700 (PDT) Received: from mail.dnt.ro (ns.dnt.ro [193.226.100.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA23060 for ; Thu, 29 Jul 1999 07:30:44 -0700 (PDT) Received: from dnt.ro (mescalito.dnt.ro [193.226.100.55]) by mail.dnt.ro (8.9.3/8.9.3) with ESMTP id RAA05796; Thu, 29 Jul 1999 17:37:05 +0300 Message-ID: <37A06747.EE828302@dnt.ro> Date: Thu, 29 Jul 1999 17:37:59 +0300 From: Stefanita Vilcu Organization: Dynamic Network Technologies, Bucuresti X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-workers@greatcircle.com CC: Jason L Tibbitts III Subject: mj2 digest problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi, I have some problems with digests on latest MJ2 CVS. Actually my digests items in the config looks like: configset shop digest_index_format = subject configset shop digests << ENDAAN digest | | | | 1w| 1d| | text Digest ENDAAN The first problem is that it sends digests in mime format, even I specified text. The second one is that I get headers in the digest messages (not only the from: and the subject: fields). In the mj_trigger.debug file I get: -== Use of uninitialized value at blib/lib/Mj/Digest.pm (autosplit into blib/lib/auto/Mj/Digest/decide.al) line 230. --== Use of uninitialized value at blib/lib/Mj/Digest.pm (autosplit into blib/lib/auto/Mj/Digest/decide.al) line 233. --== Use of uninitialized value at blib/lib/Mj/Digest.pm (autosplit into blib/lib/auto/Mj/Digest/choose.al) line 273. Where am I wrong? -vsv -- Stefanita Valeriu Vilcu, vsv@dnt.ro Technical Manager Dynamic Network Technologies Bucuresti, Romania Tel: +40-1-2106863 Fax: +40-1-3122745 From majordomo-workers-owner Thu Jul 29 07:48:35 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA23311; Thu, 29 Jul 1999 07:40:40 -0700 (PDT) Received: from mail.dnt.ro (ns.dnt.ro [193.226.100.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA23298 for ; Thu, 29 Jul 1999 07:40:26 -0700 (PDT) Received: from dnt.ro (mescalito.dnt.ro [193.226.100.55]) by mail.dnt.ro (8.9.3/8.9.3) with ESMTP id RAA06480; Thu, 29 Jul 1999 17:46:49 +0300 Message-ID: <37A0698F.CB5C850E@dnt.ro> Date: Thu, 29 Jul 1999 17:47:43 +0300 From: Stefanita Vilcu Organization: Dynamic Network Technologies, Bucuresti X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-workers@greatcircle.com CC: Jason L Tibbitts III Subject: mj2: Majordomo results: Re: C8A0-8DBE-F13E : CONSULT shopDuplica Content-Type: multipart/mixed; boundary="------------7EAB57A51ABE18B7F02BB973" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. --------------7EAB57A51ABE18B7F02BB973 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit sometimes I get such a message, that the token doesn't exist, what should I do? rgds -vsv -- Stefanita Valeriu Vilcu, vsv@dnt.ro Technical Manager Dynamic Network Technologies Bucuresti, Romania Tel: +40-1-2106863 Fax: +40-1-3122745 --------------7EAB57A51ABE18B7F02BB973 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: from list.dnt.ro (IDENT:postfix@s2.dnt.ro [193.226.100.14]) by mail.dnt.ro (8.9.3/8.9.3) with ESMTP id NAA27122 for ; Thu, 29 Jul 1999 13:16:00 +0300 Received: from s2.dnt.ro (localhost [127.0.0.1]) by list.dnt.ro (Postfix) with SMTP id 8B0441FC880 for ; Thu, 29 Jul 1999 13:16:20 +0300 (EEST) Content-Type: text/plain Content-Disposition: inline Content-Description: Results from toplevel Mime-Version: 1.0 To: Stefanita Vilcu Subject: Majordomo results: Re: C8A0-8DBE-F13E : CONSULT shopDuplica From: majordomo@list.dnt.ro Message-Id: <19990729101621.8B0441FC880@list.dnt.ro> Date: Thu, 29 Jul 1999 13:16:21 +0300 (EEST) Sender: majordomo-owner@list.dnt.ro >>>> accept **** Nonexistant token "C8A0-8DBE-F13E"! >>>> shop-owner@list.dnt.ro wrote: **** Illegal command! >>>> -- Stopping at signature separator. 1 valid command processed; its status is indeterminate. --------------7EAB57A51ABE18B7F02BB973-- From majordomo-workers-owner Thu Jul 29 08:18:12 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA23863; Thu, 29 Jul 1999 08:11:36 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA23856 for ; Thu, 29 Jul 1999 08:11:31 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA26469; Thu, 29 Jul 1999 10:16:21 -0500 To: Stefanita Vilcu Cc: majordomo-workers@greatcircle.com Subject: Re: mj2: Majordomo results: Re: C8A0-8DBE-F13E : CONSULT shopDuplica References: <37A0698F.CB5C850E@dnt.ro> From: Jason L Tibbitts III Date: 29 Jul 1999 10:16:21 -0500 In-Reply-To: Stefanita Vilcu's message of "Thu, 29 Jul 1999 17:47:43 +0300" Message-ID: Lines: 11 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "SV" == Stefanita Vilcu writes: SV> sometimes I get such a message, that the token doesn't exist, what SV> should I do? I'm not sure I understand the question. If you're saying that you get a consultation token but when you go to accept (or reject) it the token does not exist, then I'd need full debug logs from the session that created the token and the session where you're trying to accept or reject it. - J< From majordomo-workers-owner Thu Jul 29 08:34:38 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA24198; Thu, 29 Jul 1999 08:30:57 -0700 (PDT) Received: from mail.dnt.ro (ns.dnt.ro [193.226.100.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA24191 for ; Thu, 29 Jul 1999 08:30:44 -0700 (PDT) Received: from dnt.ro (mescalito.dnt.ro [193.226.100.55]) by mail.dnt.ro (8.9.3/8.9.3) with ESMTP id SAA09260; Thu, 29 Jul 1999 18:37:00 +0300 Message-ID: <37A07552.76C63AD5@dnt.ro> Date: Thu, 29 Jul 1999 18:37:54 +0300 From: Stefanita Vilcu Organization: Dynamic Network Technologies, Bucuresti X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Jason L Tibbitts III CC: majordomo-workers@greatcircle.com Subject: Re: mj2 digest problems References: <37A06747.EE828302@dnt.ro> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Jason L Tibbitts III wrote: > You're supposed to. Even with text digests you get more headers than that > (as required by the standard) but with MIME digests you get the whole > thing. Is there a way to cut this headers only to, let's say: From: Date: Subject:? > > SV> In the mj_trigger.debug file I get: > > Is this repeatable? There's not really enough information there for me to > debug this, but if it only happens once then it's probably an issue with > there not being any saved digest state. > > - J< It is happening plenty of times. A debug of 500 is enough for you to debug? thanks for your time, -vsv -- Stefanita Valeriu Vilcu, vsv@dnt.ro Technical Manager Dynamic Network Technologies Bucuresti, Romania Tel: +40-1-2106863 Fax: +40-1-3122745 From majordomo-workers-owner Thu Jul 29 08:48:17 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA23833; Thu, 29 Jul 1999 08:10:26 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA23795 for ; Thu, 29 Jul 1999 08:10:16 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA26440; Thu, 29 Jul 1999 10:14:57 -0500 To: Stefanita Vilcu Cc: majordomo-workers@greatcircle.com Subject: Re: mj2 digest problems References: <37A06747.EE828302@dnt.ro> From: Jason L Tibbitts III Date: 29 Jul 1999 10:14:55 -0500 In-Reply-To: Stefanita Vilcu's message of "Thu, 29 Jul 1999 17:37:59 +0300" Message-ID: Lines: 24 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "SV" == Stefanita Vilcu writes: SV> The first problem is that it sends digests in mime format, even I SV> specified text. That is only the default for when someone does "set list digest" (and it's possible that there is a bug there; I'll check). Regardless of what you specify, users can still choose; you can still do "set list digest-mime" or "set list digest-text". SV> The second one is that I get headers in the digest SV> messages (not only the from: and the subject: fields). You're supposed to. Even with text digests you get more headers than that (as required by the standard) but with MIME digests you get the whole thing. SV> In the mj_trigger.debug file I get: Is this repeatable? There's not really enough information there for me to debug this, but if it only happens once then it's probably an issue with there not being any saved digest state. - J< From majordomo-workers-owner Fri Jul 30 20:24:55 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA24575; Fri, 30 Jul 1999 20:13:25 -0700 (PDT) Received: from walt.toontown.erial.nj.us (s5-38.ppp.op.net [209.152.195.120]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA24568 for ; Fri, 30 Jul 1999 20:13:19 -0700 (PDT) Received: by walt.toontown.erial.nj.us (Postfix, from userid 500) id 1D3152A0D; Fri, 30 Jul 1999 23:19:43 -0400 (EDT) Date: Fri, 30 Jul 1999 23:19:39 -0400 (EDT) From: Bob Snyder To: majordomo-workers@greatcircle.com Subject: Address matching? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I just put a CVS pull of majordomo 2 into semi-production for a small list of friends. I'm running into a problem that seems a little odd. I added the address to the list as the list owner, and now when I try and get an archive file from anyone other than the list owner, it fails. However, if I generate the mail by telneting to port 25 and using the email address alone for the from, it succeeds. It looks like it's failing to match because of the comment/real name that appears in the from with the address.. Is this known/correct behavior? Bob From majordomo-workers-owner Fri Jul 30 23:19:41 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id XAA26410; Fri, 30 Jul 1999 23:10:38 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id XAA26397 for ; Fri, 30 Jul 1999 23:10:29 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id BAA20610; Sat, 31 Jul 1999 01:15:28 -0500 To: majordomo-workers@greatcircle.com, Bob Snyder Subject: Re: Address matching? References: From: Jason L Tibbitts III Date: 31 Jul 1999 01:15:27 -0500 In-Reply-To: Bob Snyder's message of "Fri, 30 Jul 1999 23:19:39 -0400 (EDT)" Message-ID: Lines: 30 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "BS" == Bob Snyder writes: BS> I added the address to the list as the list owner, I'm not quite sure what this means exactly. BS> and now when I try and get an archive file from anyone other than the BS> list owner, it fails. How does it fail? I assume you're aware that the default setting of get_access requires list membership for retrieval. Note that the list owner is never afforded any additional privilege based solely on the address; a password must be provided for that. BS> It looks like it's failing to match because of the comment/real name BS> that appears in the from with the address. It is possible, but I don't see how from reading the code. Addresses are never directly compared for string equality anywhere; even if it looks like they are, 'eq' is an overloaded operation for address objects. I'd of course like to see some debugging output; without it I can't make much sense of what's going on. BS> Is this known/correct behavior? Well, it could be, depending on information that you haven't provided. I haven't had any problems in this area, nor have I seen any other reports of problems. - J< From majordomo-workers-owner Sat Jul 31 21:49:44 1999 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA14550; Sat, 31 Jul 1999 21:33:07 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA14538 for majordomo-workers@greatcircle.com; Sat, 31 Jul 1999 21:33:05 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA25287 for ; Thu, 29 Jul 1999 09:36:52 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id LAA27572; Thu, 29 Jul 1999 11:41:42 -0500 To: Stefanita Vilcu Cc: majordomo-workers@greatcircle.com Subject: Re: mj2 digest problems References: <37A06747.EE828302@dnt.ro> <37A07552.76C63AD5@dnt.ro> From: Jason L Tibbitts III Date: 29 Jul 1999 11:41:42 -0500 In-Reply-To: Stefanita Vilcu's message of "Thu, 29 Jul 1999 18:37:54 +0300" Message-ID: Lines: 37 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3 Mime-Version: 1.0 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "SV" == Stefanita Vilcu writes: SV> Is there a way to cut this headers only to, let's say: From: Date: SV> Subject:? Not currently. First off, that violates RFC1153, which requires Date:, From:, To:, Cc:, Subject:, Message-ID:, and Keywords: (for text digests, at least). For MIME digests, the enclosed messages must be legal RFC822 messages so it is technically legal to remove everything but the minimal RFC822 headers. (I doubt the MIME module will allow this, though; after all, you can't ask it to mail out a MIME message without the MIME headers). If you want a digest to be readable without software, use a text digest and be bound to the relevant standard. MIME junk is automatically removed from them. Eventually I'll have a digest_delete_headers to parallel the delete_headers variable (because obviously keeping all of the Received: headers in a digest are excessive) and that would enable you to violate the standards all you want. SV> It is happening plenty of times. A debug of 500 is enough for you to SV> debug? Perhaps, but adding some extra output would help as well. Can you stuck something like use Data::Dumper; warn Dumper $s; warn Dumper $p; to the "decide" subroutine in lib/Mj/Digest.pl. All I'm trying to do is find out what's in those variables. My guess is that $s isn't defined, so now I have to figure out how that would be possible. Can you check to see that a "_digests" file exists for the list in question? What's in it? - J<