Re: [Mailman-Developers] Sequence of steps?
On Aug 29, 2016, at 05:46 PM, Mark Sapiro wrote:
>Here's what I've had in mm_cfg.py to do this on my production site for a
>long time
>
>#
># Put MimeDel ahead of Hold so "too big" is based on content filtered
># message.
>#
>GLOBAL_PIPELINE.remove('MimeDel')
>GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'MimeDel')
Anybody looking for something fun to do in MM3 might consider how to surface
the creation and shuffling of rule chains (moderation) and pipeline handlers
(munging) through REST so Postorius could present an easy configuration screen
for list managers.
Cheers,
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Sequence of steps?
Mark,
Thanks for your quick response. It sounds like you have this one under control.
I am far removed from anything like mm_cfg.py as I use a hosting service. I
will have to see what they think about making such a configuration change, and
how much they want to make it.
In any case, I really appreciate the help. Thanks again!
Roy
From: Mark Sapiro
To: mailman-developers@python.org
Sent: Monday, August 29, 2016 8:46 PM
Subject: Re: [Mailman-Developers] Sequence of steps?
On 08/29/2016 09:00 AM, Roy Harvey wrote:
> 3) Messages with elaborate formatting, but little text are often larger than
> 10KB, so they are held for review. That means the test for size comes BEFORE
> the message is "cleaned up" and reduced to simple text.
> My suggestion is to change the sequence of steps, so that the size filter is
> applied AFTER the message has been converted to plain text.
Yes, I agree that this is a problem, but it is easily configurable.
Here's what I've had in mm_cfg.py to do this on my production site for a
long time
#
# Put MimeDel ahead of Hold so "too big" is based on content filtered
# message.
#
GLOBAL_PIPELINE.remove('MimeDel')
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'MimeDel')
#
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Sequence of steps?
On 08/29/2016 09:00 AM, Roy Harvey wrote:
> 3) Messages with elaborate formatting, but little text are often larger than
> 10KB, so they are held for review. That means the test for size comes BEFORE
> the message is "cleaned up" and reduced to simple text.
> My suggestion is to change the sequence of steps, so that the size filter is
> applied AFTER the message has been converted to plain text.
Yes, I agree that this is a problem, but it is easily configurable.
Here's what I've had in mm_cfg.py to do this on my production site for a
long time
#
# Put MimeDel ahead of Hold so "too big" is based on content filtered
# message.
#
GLOBAL_PIPELINE.remove('MimeDel')
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'MimeDel')
#
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Sequence of steps?
I manage a Mailman list. I believe the situation I describe is not one that can be corrected by changing the configuration, but would require coding changes. (I would love to be wrong!) As such I don't expect anything to be changed, but perhaps it can end up on someone's list of requested features for eventual consideration. So here is the situation. 1) The list is text-only, so messages with fancy formatting are converted to simple text. Attachments such as photos are discarded. 2) The maximum message size is set to 10KB.* 3) Messages with elaborate formatting, but little text are often larger than 10KB, so they are held for review. That means the test for size comes BEFORE the message is "cleaned up" and reduced to simple text. My suggestion is to change the sequence of steps, so that the size filter is applied AFTER the message has been converted to plain text. I hope that is clear enough. Yes, I understand changing the order of things is No Small Thing. I figure it can't hurt to put it out there. Thanks for listening! Roy Harvey Beacon Falls, CT * (Because subscribers replying to Digest messages regularly fail to remove the text of the Digest message they are replying to, the maximum message size is set to 10KB. This also blocks messages with attached photos, which will be removed anyway because the list is text-only. I review messages held because of size. The ones with a full Digest are rejected with an explanation about removing the Digest being replied to. The ones with photos attached are rejected with an explanation about putting them on the web and posting a link. The ones that are blocked because they are long messages, or short messages with too much formatting, are approved.) ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
