FAQ
I have searched for a way to send a "server-wide" broadcast message to all
admins and subscribers and found the following (which I have yet to try):

"Send a message with an Urgent: header that contains the admin password and
it's supposed to be sent as a direct message to all subscribers"

What I find a but confusing is how to specify an "Urgent" header. Does this
person mean to say place "Urgent" in the subject line with the Admin
password? In other words, I am not sure how to specify or manipulate a
message's "header" with Mailman.

Anybody have any ideas/thoughts or am I missing something obvious?

Thanks for any and all help - Brandon

Search Discussions

  • Lindsay Haisley at Dec 21, 2009 at 7:23 pm

    On Mon, 2009-12-21 at 11:49 -0700, Brandon Rodak wrote:
    What I find a but confusing is how to specify an "Urgent" header. Does this
    person mean to say place "Urgent" in the subject line with the Admin
    password? In other words, I am not sure how to specify or manipulate a
    message's "header" with Mailman.
    This is from the code comments in the file CalcRecips.py.

    # Support for urgent messages, which bypasses digests and disabled
    # delivery and forces an immediate delivery to all members Right Now. We
    # are specifically /not/ allowing the site admins password to work here
    # because we want to discourage the practice of sending the site admin
    # password through email in the clear. (see also Approve.py)

    I would assume, from this, that the mechanism is the same as for an
    "Approved:" header or pseudo-header. If you have a mail program that
    can add arbitrary headers then you can add a true mail header, with
    "Urgent: some_password". If your mail program won't do this, you can
    use a pseudo-header by putting "Urgent: password" as the very first line
    in a post to the list ('password' is either the admin or moderator
    password. There must be no lines above this pseudo-header in the email
    body, and it must be left-justified.

    --
    Lindsay Haisley | "We are all broken | PGP public key
    FMP Computer Services | toasters, but we | available at
    512-259-1190 | still manage to make |<http://pubkeys.fmp.com>
    http://www.fmp.com | toast" |
    (Cheryl Dehut) |
  • Mark Sapiro at Dec 21, 2009 at 7:23 pm

    Brandon Rodak wrote:
    I have searched for a way to send a "server-wide" broadcast message to all
    admins and subscribers and found the following (which I have yet to try):

    "Send a message with an Urgent: header that contains the admin password and
    it's supposed to be sent as a direct message to all subscribers"

    What I find a but confusing is how to specify an "Urgent" header. Does this
    person mean to say place "Urgent" in the subject line with the Admin
    password? In other words, I am not sure how to specify or manipulate a
    message's "header" with Mailman.

    First, a few things about an 'urgent' message. This is a list function,
    not a server function. If you send an urgent message to a list, it
    only goes to the members of that list. If you send it to all lists,
    members of more that one list will be sent multiple copies.

    Also, urgent messages are not sent to owners or moderators unless they
    are also list members. To mail the owners and moderators of a list,
    send mail to LISTNAME-owner at ...

    That said, the Urgent: <password> header is just that. It must be added
    to your message as a header. Unlike Approved:, it can't be a
    pseudo-header in an initial body line, It must be a real message
    header. How you do this is a function of your MUA (mail client). Mutt
    makes it fairly easy to edit a raw message before it is sent and add
    headers. With thunderbird, you can go to Tools -> Options -> Advanced
    -> Config Editor... and add Urgent to mail.compose.other.header to add
    it to the To:, Cc:, etc pulldown list in mail composition.

    Other MUAs such as I think MS Outlook and most webmail clients do not
    provide a way to do this.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Lindsay Haisley at Dec 21, 2009 at 7:33 pm

    On Mon, 2009-12-21 at 11:23 -0800, Mark Sapiro wrote:
    That said, the Urgent: <password> header is just that. It must be added
    to your message as a header. Unlike Approved:, it can't be a
    pseudo-header in an initial body line, It must be a real message
    header.
    Thanks for the clarification. I mis-spoke in my post, just prior to
    yours, in suggesting that this might work with a pseudo-header.

    --
    Lindsay Haisley | "Never expect the people who caused a problem
    FMP Computer Services | to solve it." - Albert Einstein
    512-259-1190 |
    http://www.fmp.com |
  • Brandon Rodak at Dec 21, 2009 at 10:57 pm
    Lindsay and Mark:

    Thanks for your advice on the broadcast message and how to add the
    appropriate header. I guess my next question would be if it is possible at
    all to send such a broadcast message to all lists (and thus all list
    members) at one time. I have 60 + distinct/unique lists and would not want
    to send the same message sixty times if I did not have to - Any ideas?

    Thanks again - Brandon
  • Mark Sapiro at Dec 21, 2009 at 11:43 pm

    Brandon Rodak wrote:
    Thanks for your advice on the broadcast message and how to add the
    appropriate header. I guess my next question would be if it is possible at
    all to send such a broadcast message to all lists (and thus all list
    members) at one time. I have 60 + distinct/unique lists and would not want
    to send the same message sixty times if I did not have to - Any ideas?

    bin/find_member . | grep -v "^ " | sed "s/ found in://" | \
    xargs mail < message_file -s "The Subject"

    If you want to include owners and moderators who aren't list members,

    #!bin/sh
    bin/find_member . | grep -v "^ " | sed "s/ found in://" > member_file
    bin/list_owners -m > owner_moderator_file
    sort -u member_file owner_moderator_file | \
    xargs mail < message_file -s "The Subject"


    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Stephen J. Turnbull at Dec 22, 2009 at 12:43 am
    Brandon Rodak writes:
    members) at one time. I have 60 + distinct/unique lists and would not want
    to send the same message sixty times if I did not have to - Any ideas?
    Make an umbrella list, ie, the subscribers are the 60+ lists.
    Optionally add the LIST-owner addresses. Set it up as announce-only.

    The main glitch here is that the umbrella list will probably clean out
    the Urgent header since it contains a password, and the 60+ lists will
    deliver the message as usual (including digest processing if the users
    have that enabled. Fixing this (if I am correct) would probably
    require customizing the Mailman code a bit.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedDec 21, '09 at 6:49p
activeDec 22, '09 at 12:43a
posts7
users4
websitelist.org

People

Translate

site design / logo © 2022 Grokbase