Revisit to moderator aliases
Hi Steve, et al,
Awhile back I asked some questions about managing my Mailman list such that it worked like it did back on Autoshare (an old Mac OS 9 listserver). I received some good advice, and have made some great progress in attaining most of my goals. There were still some unresolved issues, but I took a break to let others on the list tackle their problems, and also to let myself digest (no pun intended) the situation for awhile.
To recap, I have a mailing list of about 300 members. The reply-to is currently customized to go to one of my personal email addresses (versus the mailmon default address of <foo-list@lists.sonic.net>). When I receive the posts, I determine whether the post is appropriate for the list, and if needed, edit out extraneous text (such as excessive quoted material and/or excessive signature lines) as well as profanity or classified information that doesn't belong on the list. I then use Eudora's "redirect" function (keeps headers in tact) to redirect the moderated post to foo-list@lists.sonic.net.
The two outstanding issues are:
After I do the redirect to foo-list@lists.sonic.net, the listserver still sends the moderation email back to me, requiring me to approve of the post (despite the fact that the envelope sender is from the list owner/moderator). When the list traffic is slow, this isn't a big issue, but when topics get hot, this becomes a major headache (receive, read, modify, send, receive again, approve).
Replies to digest still automatically go to foo-list@lists.sonic.net instead of to the customized reply-to address (and there does not appear to be any way to change that). This becomes a mess because now I have a mix of non-moderated posts and moderated posts in the same place, so I have to be careful about which ones I approve.
DREAM SOLUTION: I'm looking for a solution that would resolve both these issues. I imagine a solution where I set the reply-to address to foo-list@lists.sonic.net, but somehow get the list to send those posts to me intact unmodified (versus getting the Mailman generated moderator emails with all the extraneous stuff and extra headers). Then I perform any necessary modifications, and redirect to the list, with the original heads intact, but have the list recognize the envelope sender and therefore post to the list (rather than bounce back to the moderator).
I don't know if the first part of this solution is possible. However, I believe I've already received information that tells me that the 2nd part is not possible because Mailman does not have a "check the envelope sender first" option. Experimentation has shown me that if I send a post to the list, and the FROM sender is not a member, but the envelope sender the moderator (aka, me), it passes it through to the list. However, if the FROM sender is a member (but mod flag turned on), then Mailman holds the post for moderator approval regardless of what the envelope sender is.
The FROM sender will always be a member of the list, and I want to keep the FROM sender intact; hence, unless I'm the member posting, it will always be held for moderation.
In one of the earlier replies, Steve suggested the following aliases:
foo-list: moderator@example.com foo-list-moderated: | mailman post foo-list
This suggestion sounds a bit like the first part of my "dream" solution above, where I let people post to the list address (instead of the customized reply-to address). The alias would then route the post directly to me rather than to Mailman. Putting aside, for now, how I get this alias set up, I'm still stuck on how I would then get the email posted to the mailing list (since if I send it to the list address, it will just come back to me again). Perhaps that is where the foo-list-moderated alias comes into play?
Taking a stab at it, I should ask my ISP to do the following:
- Set an alias for foo-list@lists.sonic.net to go to moderator@example.com (my email).
- Set an alias for foo-list-moderated@lists.sonic.net to go to "| mailman post foo-list".
Then my steps for moderating the list would be:
Receive email at moderator@example.com (originally posted to foo-list@lists.sonic.net), perform edits as necessary, then redirect the post to foo-list-moderated@lists.sonic.net (6 steps down to 3 steps).
I did a test email to foo-list-moderated@lists.sonic.net, and it was returned as "no such user", so I'm guessing that I'm actually creating a new email alias as part of this solution.
Does it sound like I understand the suggestion correctly? And if so, is it the solution that you think I am after?
I just want to make sure I'm on the right track before I start poking my ISP for help.
THANKS!!
Bill
Bill Catambay wrote:
Your posts arrived out of sequence due to greylisting at python.org, so I've responded to this, and Stephen, as is often the case, has an even better idea.
I don't recall if we covered custom handlers in the earlier thread, but there is a FAQ at <http://wiki.list.org/x/l4A9> that talks about installing a custom handler for a single list. That FAQ talks about adding a handler to the pipeline, but what you would want is to replace the Moderate handler with your own version. Yours would differ from the base by changing the initial part of process() from
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(): if mlist.isMember(sender): break else: sender = None
to
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(headers=(None, 'from', 'reply-to', 'sender')): if mlist.isMember(sender): break else: sender = None
Actually, you could use any sequence of headers (and None for envelope sender) you want, You could check just the envelope sender with
for sender in msg.get_senders(headers=(None,))Then you (the host actually) would replace Moderate with this handler in a custom pipeline for this list only.
Exactly. foo-list: becomes an alias for you and foo-list-moderated: becomes the actual list posting address. Or, you (read the host) could make the foo-list: alias like
foo-list: "|/path/to/mailman/mail/mailman owner foo-list"
so it would be a synonym for foo-list-owner and you wouldn't have to bug the host if you wanted to change the address (note Stephen's foo-list-moderated: is abbreviated and really should look more like this one but with the 'post' argument he has).
Right.
Does it sound like I understand the suggestion correctly? And if so, is it the solution that you think I am after?
Yes.
I just want to make sure I'm on the right track before I start poking my ISP for help.
I think the aliases together with the modified Moderate handler for your list will be your DREAM SOLUTION. And this has the advantage that while it is some work for the host to set up, it affects only your list so thay can't say no solely on the grounds that it may have unintended consequences for other customers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Looks like I'm half-way there.... unfortunately, half-way means "one step back" before the "two steps forward".
I got my ISP to create the aliases:
foo-list: "|/opt/mailman/mail/mailman owner foo-list" foo-list-mod: "|/opt/mailman/mail/mailman post foo-list"
It would appear that there is one more thing they need to do, because when I try to send an email to the foo-list-mod address, I get a hard bounce:
----- The following addresses had permanent fatal errors -----<foo-list-mod@lists.sonic.net> (reason: 550 5.1.1 <foo-list-mod@lists.sonic.net>... No such user here)
I just got off the phone with their evening tech support person, but he doesn't have a clue. He confirmed that the aliases were set up, but he doesn't know what else to do to complete the task so that foo-list-mod email is an actual working email address (and I don't know what to tell him so that he would know what to do).
The reason why I've gone backwards is because the first alias change *is* working, which means that there is currently no email address which is actually posting to the list. Doh! The list is dead, Jim.
(the evening tech guy said he didn't have authority to update aliases for mailing lists, so he couldn't back out the change)
Here's a couple of questions while I sit idly by as posts to the mailing list build up in my inbox:
Anyone know the missing ingredient (in tech terms) that might clue in the "night watchman" on what needs to be done to make foo-list-mod work?
Is there anyway to get posts posted to a mailing list when there is no email address which does it?
I have high hopes that *eventually* this mailing list will get to where I need it to be, but given that the weekend is upon us, I'm currently looking for something to get the list working in the meantime.
Thanks, Bill
At 7:48 PM -0800 on 11/17/09, Mark Sapiro wrote:
Bill Catambay wrote:
This might not be helpful, depending on the mail server, but has someone run "newaliases" to make sure those aliases in the file have actually been made active?
(This isn't a necessary step for all mail servers, but it seems likely given your bounce message. Goodness knows I forgot to do it a few times back when I was using sendmail on my list server.)
Terri
At 11:42 PM -0500 on 11/20/09, Terri Oda wrote:
The night tech guy confirmed that they are active (although I don't know how he confirmed it). Given that there were two alias changes, and since I *know* that the first alias did take effect (i.e., the foo-list email now comes to me instead of posting to the list), I'd assume that the 2nd alias took effect. Also, they're both in a file (along with other mailing list related aliases), and I believe they processed that file of aliases (rather than doing each alias manually).
At this point, I wish the aliases did not take effect, because then I'd at least still be able to get posts to the mailing list.
Bill
andale@excaliburworld.com wrote:
The lists.sonic.net domain has 2 MXs (mailin-01.mx.sonic.net and mailin-02.mx.sonic.net) and each of those has 4 IP addresses, so there are potentially 8 servers that can receive the domain's mail.
I'm guessing, but I suspect the aliases were changed on the Mailman server so thay mail that reaches that server for foo-list and foo-list-mod will be properly handled, but the missing piece is relaying the mail from the 8 MX servers to the Mailman server. This was already being done for the foo-list address so changing that alias on the Mailman host worked, but foo-list-mod is not an address that the 8 MXs know to relay to the Mailman server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
At 7:48 PM -0800 on 11/17/09, Mark Sapiro wrote:
Oh, and I forgot to ask about the "modified Moderate handler" (basically because I just now noticed - when my head doesn't immediately pick up on an idea, I skim past it). Since I didn't actually mention anything about modifying a handler in my request to my host, am I still missing a critical piece of the puzzle? I guess when the foo-list-mod email starts to work, it's still going to result in the same behavior as before... in that it will see the FROM address first, which will be a member with the mod flag set, and hold the post for approval.
*sigh* LOL *sigh*
So I need to ask them to install a custom handler for the foo-list (my) mailing list (and God willing, they'll understand what that means). I'll tell them to change:
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(): if mlist.isMember(sender): break else: sender = None
to:
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(headers=(None,)): if mlist.isMember(sender): break else: sender = None
(i think just checking envelope sender is all I need since I'm the only one who will know about this email)(well, me and everyone on this mailing list ;))
I hope someone there knows how to do this, otherwise this has all been in vain.
Bill
Bill Catambay wrote:
They need to do the following:
Copy Mailman/Handlers/Moderate.py to Mailman/Handlers/Moderate_foo.py
Edit Moderate_foo.py as above
This step can be done in multiple ways, but perhaps the easiest to explain is as follows:
Create the file extend.py in the lists/foo-list/ directory (the already existing directory that contains the foo-list config.pck, etc.) The contents of this file are the 5 lines:
import copy from Mailman import mm_cfg def extend(mlist): mlist.pipeline = copy.copy(mm_cfg.GLOBAL_PIPELINE) mlist.pipeline[mlist.pipeline.index('Moderate')] = 'Moderate_foo'
See the FAQ at <http://wiki.list.org/x/l4A9> for more detail.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Okay, today was quite the rollercoaster. I finally got an email from my ISP's Operations group stating that the foo-list-mod email was working, but when I tried, it didn't work. Bounced just like before. I called them up, and when I told them it was still bouncing, they insisted that it was working, and said there was nothing further they could do for me. At that point, I lost it, and despite a great track record they had for customer support, I laid into them. It was like Jekyll turning into Hyde. After stating that the mailing list was down for 4 days, and that it was still not working, along with a few other "choice" things I said about their level of support on this occasion, he said he would find a supervisor and find a resolution to the problem.
An hour later, I got an email indicating that they had fixed the problem. Apparently, they created the foo-list-mod under an old listman sub-domain, rather than the "lists" sub-domain that everyone is using. Once they fixed that, and foo-list-mod started working.
Given that they were ready to shut the door on this before even getting the alias fixed (not to mention that he added a blurb about how they probably should not have supported the request in the first place), I'm not hopeful that they are going to do anything with the customization request.
What I think I'll do is just remove the MOD flags on everyone (since no one knows about the special mod email)(yet). I might start looking at installing Mailman on my OS X server (which is already running EIMS 3.3).
In any case, I did have one follow-up question (suggestion, actually, from a member of my list). In the digests, is there any setting that is available to *me* that will let me put the digest prolog text (e.g., "To subscribe..., When replying..., etc., etc.) at the bottom of the digest instead of the top? As the member stated, they see this info constantly, but doesn't need to be read often, and it gets in the way with the front of the digest that they are interested in.
Thanks, Bill
Bill Catambay wrote:
How about changing the text?
The text is built from the masthead.txt template. A list specific version of this template can be installed (see the FAQ at <http://wiki.list.org/x/jYA9>), but not by *you* (unless you start running your own Mailman). This is not one of the 4 templates that can be edited through the list admin GUI, so the host would have to install it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 23-Nov-2009, at 17:21, Mark Sapiro wrote:
Heh. SHort and concise.
I THINK that the "No" really means that it is not possible. The Digest messages are sent out as multi-part mime messages. Each message in the digest is a separate mime part. The text of the actual message is the thing that appears to be a 'header' to your and your user, but it is not the header, it is the body of the message.
What I would recommend is making sure your client understands the mime digest format and can properly 'explode' it into individual messages. This way you never have to worry about the 'header'
-- If fashion is your trade then when you're naked I guess you must be unemployed.
LuKreme wrote:
I THINK that the "No" really means that it is not possible.
Not without modifying the source code.
The Digest messages are sent out as multi-part mime messages. Each message in the digest is a separate mime part. The text of the actual message is the thing that appears to be a 'header' to your and your user, but it is not the header, it is the body of the message.
This is true of the MIME format digests, but list members can chose a plain text digest which is a single text/plain part containing the masthead, the table of contents and the (scrubbed) messages, and which in a default installation with default list settings is the default digest format.
What I would recommend is making sure your client understands the mime digest format and can properly 'explode' it into individual messages. This way you never have to worry about the 'header'
And list owners and other list members would never have to deal with posts with Subject: Re: listname Digest, Vol nn, Issue nn and bodies consisting of "Yeah, me too" followed by a quote of the entire digest.
</rant>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 23-Nov-2009, at 17:53, Mark Sapiro wrote:
I'm hoping that in MM3 when someone does this a couple of things happen:
- the message is not posted
- they get a note from the list saying don't do that
- their mod bit is enabled.
-- You know, Rick, I have many a friend in Casablanca, but somehow, just because you despise me, you are the only one I trust.
Why would HTML messages sent to the list be chanegd to plain text when I have content filtering turned off via the GUI? Is it possible the GUI switch is not working? If yes, how can I check 'under the hood'? Thank you in advance.
christian stalberg wrote:
If filter_content is no, Mailman should not be doing any content filtering or HTML to plain text conversion.
I can make a guess. Perhaps the message is multipart/alternative with text/plain and text/html alternative parts and you are viewing the received message with an MUA (mail client) set to show you the plain text, or perhaps you are seeing a 'scrubbed' message in a digest or the archive or even the message from the list if Non-digest options -> scrub_nondigest is set to Yes.
If you really want to look 'under the hood' look at the output from
bin/config_list -o - LISTNAME
or
bin/dumpdb lists/LISTNAME/config.pck | grep filter_content
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Bill Catambay wrote:
Your posts arrived out of sequence due to greylisting at python.org, so I've responded to this, and Stephen, as is often the case, has an even better idea.
I don't recall if we covered custom handlers in the earlier thread, but there is a FAQ at <http://wiki.list.org/x/l4A9> that talks about installing a custom handler for a single list. That FAQ talks about adding a handler to the pipeline, but what you would want is to replace the Moderate handler with your own version. Yours would differ from the base by changing the initial part of process() from
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(): if mlist.isMember(sender): break else: sender = None
to
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(headers=(None, 'from', 'reply-to', 'sender')): if mlist.isMember(sender): break else: sender = None
Actually, you could use any sequence of headers (and None for envelope sender) you want, You could check just the envelope sender with
for sender in msg.get_senders(headers=(None,))Then you (the host actually) would replace Moderate with this handler in a custom pipeline for this list only.
Exactly. foo-list: becomes an alias for you and foo-list-moderated: becomes the actual list posting address. Or, you (read the host) could make the foo-list: alias like
foo-list: "|/path/to/mailman/mail/mailman owner foo-list"
so it would be a synonym for foo-list-owner and you wouldn't have to bug the host if you wanted to change the address (note Stephen's foo-list-moderated: is abbreviated and really should look more like this one but with the 'post' argument he has).
Right.
Does it sound like I understand the suggestion correctly? And if so, is it the solution that you think I am after?
Yes.
I just want to make sure I'm on the right track before I start poking my ISP for help.
I think the aliases together with the modified Moderate handler for your list will be your DREAM SOLUTION. And this has the advantage that while it is some work for the host to set up, it affects only your list so thay can't say no solely on the grounds that it may have unintended consequences for other customers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Looks like I'm half-way there.... unfortunately, half-way means "one step back" before the "two steps forward".
I got my ISP to create the aliases:
foo-list: "|/opt/mailman/mail/mailman owner foo-list" foo-list-mod: "|/opt/mailman/mail/mailman post foo-list"
It would appear that there is one more thing they need to do, because when I try to send an email to the foo-list-mod address, I get a hard bounce:
----- The following addresses had permanent fatal errors -----<foo-list-mod@lists.sonic.net> (reason: 550 5.1.1 <foo-list-mod@lists.sonic.net>... No such user here)
I just got off the phone with their evening tech support person, but he doesn't have a clue. He confirmed that the aliases were set up, but he doesn't know what else to do to complete the task so that foo-list-mod email is an actual working email address (and I don't know what to tell him so that he would know what to do).
The reason why I've gone backwards is because the first alias change *is* working, which means that there is currently no email address which is actually posting to the list. Doh! The list is dead, Jim.
(the evening tech guy said he didn't have authority to update aliases for mailing lists, so he couldn't back out the change)
Here's a couple of questions while I sit idly by as posts to the mailing list build up in my inbox:
Anyone know the missing ingredient (in tech terms) that might clue in the "night watchman" on what needs to be done to make foo-list-mod work?
Is there anyway to get posts posted to a mailing list when there is no email address which does it?
I have high hopes that *eventually* this mailing list will get to where I need it to be, but given that the weekend is upon us, I'm currently looking for something to get the list working in the meantime.
Thanks, Bill
At 7:48 PM -0800 on 11/17/09, Mark Sapiro wrote:
Bill Catambay wrote:
This might not be helpful, depending on the mail server, but has someone run "newaliases" to make sure those aliases in the file have actually been made active?
(This isn't a necessary step for all mail servers, but it seems likely given your bounce message. Goodness knows I forgot to do it a few times back when I was using sendmail on my list server.)
Terri
At 11:42 PM -0500 on 11/20/09, Terri Oda wrote:
The night tech guy confirmed that they are active (although I don't know how he confirmed it). Given that there were two alias changes, and since I *know* that the first alias did take effect (i.e., the foo-list email now comes to me instead of posting to the list), I'd assume that the 2nd alias took effect. Also, they're both in a file (along with other mailing list related aliases), and I believe they processed that file of aliases (rather than doing each alias manually).
At this point, I wish the aliases did not take effect, because then I'd at least still be able to get posts to the mailing list.
Bill
andale@excaliburworld.com wrote:
The lists.sonic.net domain has 2 MXs (mailin-01.mx.sonic.net and mailin-02.mx.sonic.net) and each of those has 4 IP addresses, so there are potentially 8 servers that can receive the domain's mail.
I'm guessing, but I suspect the aliases were changed on the Mailman server so thay mail that reaches that server for foo-list and foo-list-mod will be properly handled, but the missing piece is relaying the mail from the 8 MX servers to the Mailman server. This was already being done for the foo-list address so changing that alias on the Mailman host worked, but foo-list-mod is not an address that the 8 MXs know to relay to the Mailman server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
At 7:48 PM -0800 on 11/17/09, Mark Sapiro wrote:
Oh, and I forgot to ask about the "modified Moderate handler" (basically because I just now noticed - when my head doesn't immediately pick up on an idea, I skim past it). Since I didn't actually mention anything about modifying a handler in my request to my host, am I still missing a critical piece of the puzzle? I guess when the foo-list-mod email starts to work, it's still going to result in the same behavior as before... in that it will see the FROM address first, which will be a member with the mod flag set, and hold the post for approval.
*sigh* LOL *sigh*
So I need to ask them to install a custom handler for the foo-list (my) mailing list (and God willing, they'll understand what that means). I'll tell them to change:
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(): if mlist.isMember(sender): break else: sender = None
to:
def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return # First of all, is the poster a member or not? for sender in msg.get_senders(headers=(None,)): if mlist.isMember(sender): break else: sender = None
(i think just checking envelope sender is all I need since I'm the only one who will know about this email)(well, me and everyone on this mailing list ;))
I hope someone there knows how to do this, otherwise this has all been in vain.
Bill
Bill Catambay wrote:
They need to do the following:
Copy Mailman/Handlers/Moderate.py to Mailman/Handlers/Moderate_foo.py
Edit Moderate_foo.py as above
This step can be done in multiple ways, but perhaps the easiest to explain is as follows:
Create the file extend.py in the lists/foo-list/ directory (the already existing directory that contains the foo-list config.pck, etc.) The contents of this file are the 5 lines:
import copy from Mailman import mm_cfg def extend(mlist): mlist.pipeline = copy.copy(mm_cfg.GLOBAL_PIPELINE) mlist.pipeline[mlist.pipeline.index('Moderate')] = 'Moderate_foo'
See the FAQ at <http://wiki.list.org/x/l4A9> for more detail.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Okay, today was quite the rollercoaster. I finally got an email from my ISP's Operations group stating that the foo-list-mod email was working, but when I tried, it didn't work. Bounced just like before. I called them up, and when I told them it was still bouncing, they insisted that it was working, and said there was nothing further they could do for me. At that point, I lost it, and despite a great track record they had for customer support, I laid into them. It was like Jekyll turning into Hyde. After stating that the mailing list was down for 4 days, and that it was still not working, along with a few other "choice" things I said about their level of support on this occasion, he said he would find a supervisor and find a resolution to the problem.
An hour later, I got an email indicating that they had fixed the problem. Apparently, they created the foo-list-mod under an old listman sub-domain, rather than the "lists" sub-domain that everyone is using. Once they fixed that, and foo-list-mod started working.
Given that they were ready to shut the door on this before even getting the alias fixed (not to mention that he added a blurb about how they probably should not have supported the request in the first place), I'm not hopeful that they are going to do anything with the customization request.
What I think I'll do is just remove the MOD flags on everyone (since no one knows about the special mod email)(yet). I might start looking at installing Mailman on my OS X server (which is already running EIMS 3.3).
In any case, I did have one follow-up question (suggestion, actually, from a member of my list). In the digests, is there any setting that is available to *me* that will let me put the digest prolog text (e.g., "To subscribe..., When replying..., etc., etc.) at the bottom of the digest instead of the top? As the member stated, they see this info constantly, but doesn't need to be read often, and it gets in the way with the front of the digest that they are interested in.
Thanks, Bill
Bill Catambay wrote:
How about changing the text?
The text is built from the masthead.txt template. A list specific version of this template can be installed (see the FAQ at <http://wiki.list.org/x/jYA9>), but not by *you* (unless you start running your own Mailman). This is not one of the 4 templates that can be edited through the list admin GUI, so the host would have to install it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 23-Nov-2009, at 17:21, Mark Sapiro wrote:
Heh. SHort and concise.
I THINK that the "No" really means that it is not possible. The Digest messages are sent out as multi-part mime messages. Each message in the digest is a separate mime part. The text of the actual message is the thing that appears to be a 'header' to your and your user, but it is not the header, it is the body of the message.
What I would recommend is making sure your client understands the mime digest format and can properly 'explode' it into individual messages. This way you never have to worry about the 'header'
-- If fashion is your trade then when you're naked I guess you must be unemployed.
LuKreme wrote:
I THINK that the "No" really means that it is not possible.
Not without modifying the source code.
The Digest messages are sent out as multi-part mime messages. Each message in the digest is a separate mime part. The text of the actual message is the thing that appears to be a 'header' to your and your user, but it is not the header, it is the body of the message.
This is true of the MIME format digests, but list members can chose a plain text digest which is a single text/plain part containing the masthead, the table of contents and the (scrubbed) messages, and which in a default installation with default list settings is the default digest format.
What I would recommend is making sure your client understands the mime digest format and can properly 'explode' it into individual messages. This way you never have to worry about the 'header'
And list owners and other list members would never have to deal with posts with Subject: Re: listname Digest, Vol nn, Issue nn and bodies consisting of "Yeah, me too" followed by a quote of the entire digest.
</rant>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 23-Nov-2009, at 17:53, Mark Sapiro wrote:
I'm hoping that in MM3 when someone does this a couple of things happen:
- the message is not posted
- they get a note from the list saying don't do that
- their mod bit is enabled.
-- You know, Rick, I have many a friend in Casablanca, but somehow, just because you despise me, you are the only one I trust.
Why would HTML messages sent to the list be chanegd to plain text when I have content filtering turned off via the GUI? Is it possible the GUI switch is not working? If yes, how can I check 'under the hood'? Thank you in advance.
christian stalberg wrote:
If filter_content is no, Mailman should not be doing any content filtering or HTML to plain text conversion.
I can make a guess. Perhaps the message is multipart/alternative with text/plain and text/html alternative parts and you are viewing the received message with an MUA (mail client) set to show you the plain text, or perhaps you are seeing a 'scrubbed' message in a digest or the archive or even the message from the list if Non-digest options -> scrub_nondigest is set to Yes.
If you really want to look 'under the hood' look at the output from
bin/config_list -o - LISTNAME
or
bin/dumpdb lists/LISTNAME/config.pck | grep filter_content
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (6)
-
andale＠excaliburworld.com -
Bill Catambay
-
christian stalberg -
LuKreme -
Mark Sapiro -
Terri Oda