Site administrative broadcast to all lists and all list members - server wide
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
On Mon, 2009-12-21 at 11:49 -0700, Brandon Rodak wrote:
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) |
Brandon Rodak wrote:
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@...
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, 2009-12-21 at 11:23 -0800, Mark Sapiro wrote:
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 |
On Mon, 2009-12-21 at 11:49 -0700, Brandon Rodak wrote:
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) |
Brandon Rodak wrote:
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@...
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, 2009-12-21 at 11:23 -0800, Mark Sapiro wrote:
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 |
participants (3)
-
Brandon Rodak -
Lindsay Haisley -
Mark Sapiro