Dan Simoes <email@example.com> writes:
# I found it confusing with all the different lists
# majordomo can handle, so I made up a table, and eventually
# a doc. Notice the useage of list-owner and list-approval.
# Are these roles correctly defined?
Well, sort of. First, you need to make the distinction between
managing the list and managing postings to the list. The "open",
"closed", "auto", "private" stuff all involves managing the list, NOT
managing what's sent to the list.
Second, Majordomo doesn't know anything about "-owner" addresses;
Majordomo knows only about "-approval" addresses. Resend doesn't even
know that much; it knows only about what you tell it on the command line.
It sends problem reports and such to whatever address the "-f" flag
specifies; if there isn't one, it sends to "<list>-request" (<list> is
specified by the "-l" flag, which is a required flag for resend).
So, the role of "-approve", "-owner", and so forth depends on how you
set up your aliases.
# NOTE: resend options
# By using resend in conjunction with majordomo, you can alter the behavior
# of any of the above lists:
# - A list is unmoderated by default, where all submissions by list members
# are automatically sent to the list. By using resend with the -a/-A flags,
# the list can be moderated, where all submissions are bounced to
# list-approval for approval.
No, they're bounced to whatever address is specified with the "-f"
flag to "resend" (or to "<list>-request" if there is no "-f" flag).
# - A list will accept non-member submissions by default, which will
# immediately be distributed to the entire list. By using resend with
# the -I <list> flag, submissions by non-list members are bounced to
Note that "-A" overrides "-I". Again, they're bounced to whatever is
specified by the "-f" flag to "resend".
Brent Chapman Great Circle Associates
Brent@GreatCircle.COM 1057 West Dana Street
+1 415 962 0841 Mountain View, CA 94041