Re: [Mailman-Users] Part of moderated mails postponed to later digests

[Henrik Rasmussen]

> My best guess is you are triggering digests on size (Digest options -> 
> digest_size_threshold) and either not periodically (digest_send_periodic = 
> No) or cron/senddigests runs only weekly.

To clarify, he has set digest_size_threshold to 1 and digest_send_periodic 
=Yes. /usr/lib/mailman/cron/senddigests is run by cron every day at noon.

Other digest settings is

nondigestable = True
scrub_nondigest = False
digestable = True
digest_is_default = 1
mime_is_default_digest = 0
digest_size_threshhold = 1
digest_send_periodic = 1
digest_volume_frequency = 3
discard_these_nonmembers = (241 members)
ban_list = (188 members)

The digest_size_threshhold = 1 may likely course the problem, but is 
necessary as a digest containing a single mail is sent each time a mail is sent 
to the list-address as suggested by 
https://mail.python.org/pipermail/mailman-users/2014-August/077622.html.

Regards Henrik
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] 64 bit encoding

[Stephen J. Turnbull]

Mark Sapiro writes:

 > +email.Charset.add_charset('utf-8',
 > +  email.Charset.SHORTEST,
 > +  email.Charset.QP,
 > +  'utf-8')

I don't know if this actually is available, let alone whether it would
work (might affect headers, too, and of course elderly recipient
systems might throw a tantrum), but how about Content-Transfer-Encoding
of 8bit?

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] [Mailman-Developers] Mailman and Box

[Stephen J. Turnbull]

Moving to mailman-users, be a better place to post a request for
experience.

Please respect cross-posting restrictions.  If you're just reporting
experience, reply-to is set to Mailman-Users which is appropriate (at
least, IIRC the Mailman Users/Developers lists don't mess with
preexisting Reply-To).  If you have patched Mailman to make it work
better in this kind of application, you *may* wish to move the
conversation back to Mailman Developers to propose inclusin in a
future version of Mailman.  (If you just want to say "hey I have a
patch", I would leave that on -Users, FWIW YMMV.)

bill.co...@unh.edu writes:
 > We will be retiring our Blackboard system (an e-learning portal)
 > which offered users 'organizations'; basically a combination of
 > group sharing of documents and collaboration via email.
 > 
 > I can't begin to duplicate all of the functionality of this part
 > of Blackboard, but I figured if I could link our school's Box
 > cloud storage with our new Mailman v2 installation, that would go
 > a long ways to provide a similar service.
 > 
 > The idea is that for every Mailman list created, a new Box shared
 > folder would also be created and associated with that list.  The
 > list owner and subscriber information would live in Mailman.  A
 > nightly reconciliation job would maintain the
 > list-owner/folder-owner roster and subscriber list between the
 > two systems.  Subscribers to the list would be granted, as a
 > whole, either reader or contributor access to the Box folder
 > (whatever the owner chooses).  The list-owner would be able to do
 > things like put the associated Box folder's URL into the list's
 > message footer.
 > 
 > Box provides a RESTful API, so I think I just might be able to
 > pull this off.
 > 
 > My question is, is there anybody else already doing this or
 > something similar?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] 64 bit encoding

[Mark Sapiro]

On 11/04/2015 04:27 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
> 
>  > +email.Charset.add_charset('utf-8',
>  > +  email.Charset.SHORTEST,
>  > +  email.Charset.QP,
>  > +  'utf-8')
> 
> I don't know if this actually is available, let alone whether it would
> work (might affect headers, too, and of course elderly recipient
> systems might throw a tantrum), but how about Content-Transfer-Encoding
> of 8bit?


I did test it and it does work. I didn't think of it at the time, but
replacing the body encoding (email.Charset.QP in the above patch) with
None, i.e.

email.Charset.add_charset('utf-8',
  email.Charset.SHORTEST,
  None,
  'utf-8')

also works and produces a message with

Content-Transfer-Encoding: 8bit

It doesn't affect headers. The arguments are character set, header
encoding, body encoding, output codec. The only thing the add_charset in
the patch changes from the default is the body encoding argument.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] 64 bit encoding

[Ruben Safir]

I'm converting my mailing lists from majordomo to mailman using postfix.
 A lot of little issues have cropped up but the biggest problem I have
currently is that it seems that mailman is converting files to 64 bit
which is screwing up my home cooked archives but good.

How you I stop it from doing this:


 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: hangout-boun...@nylxs.com
Sender: "hangout" 

T24gMTEvMDMvMjAxNSAxMTozOCBBTSwgUnViZW4gU2FmaXIgd3JvdGU6Cj4gTG93IGxldmVsIGF1
dG9tYXRpb24gdG9vbHMgZGV2ZWxvcGVyCj4g16nXnNeXINen15XXqNeV16og15fXmdeZ150KPiDX
lNeV16HXoyDXnNeh15wKPiBEZXZhbG9yZUV4cGVyaWVuY2VkIHdpdGggdG9vbHMgYW5kIGF1dG9t
YXRpb24gZnJhbWV3b3JrIGRldmVsb3BtZW50IGZvcgo+IGxvdyBsZXZlbCBzb2Z0d2FyZSBGVy9k
cml2ZXIKPiBFeGNlbGxlbnQgdW5kZXJzdGFuZGluZyBjb21wbGljYXRlZCBvZiBTVyBhcmNoaXRl
Y3R1cmUgSFcvRHJpdmVyL1NXCj4gKEV4Y2VsbGVudCBrbm93bGVkZ2UgaW4gQysrICg0KyB5ZWFy
cwo+IEdvb2Qga25vd2xlZGdlIGluIEMjIGFuZCBPT1AgLSBhZHZhbnRhZ2UgMisgeWVhcnMKPiBE
ZWVwIHVuZGVyc3RhbmRpbmcgaW4gTGludXggaW50ZXJuYWxzCj4gSGFuZHMgb24gSmF2YSBwcm9n
cmFtbWluZyBleHBlcmllbmNlCj4gQWR2YW50YWdlIDpGYW1pbGlhcml0eSB3aXRoIG5ldHdvcmtp
bmcgc3lzdGVtL3Byb3RvY29scwo+IEFkdmFudGFnZSA6RXhwZXJpZW5jZSB3aXRoIE9iamVjdCBP
cmllbnRlZCBtZXRob2RvbG9naWVzCj4gKEJpZyBBZHZhbnRhZ2UgOkZhbWlsaWFyaXR5IHdpdGgg
V2ktRmkgdGVjaG5vbG9naWVzICg4MDIuMTEKPiBHb29kIGRlYnVnZ2luZyBhbmQgcHJvYmxlbSBz
b2x2aW5nIHNraWxscwo+IEdvb2QgY29tbXVuaWNhdGlvbiBza2lsbHMgYW5kIGFiaWxpdHkgJiBk
ZXNpcmUgdG8gd29yayBhcyBhIHRlYW0gcGxheWVyCj4gYXJlIGEgbXVzdAo+IFRoZXNlIHBvc2l0
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Part of moderated mails postponed to later digests

[Mark Sapiro]

On 11/04/2015 02:09 AM, Henrik Rasmussen wrote:
>> My best guess is you are triggering digests on size (Digest options -> 
>> digest_size_threshold) and either not periodically (digest_send_periodic = 
>> No) or cron/senddigests runs only weekly.
> 
> To clarify, he has set digest_size_threshold to 1 and 
> digest_send_periodic =Yes. /usr/lib/mailman/cron/senddigests is run by cron 
> every day at noon.
> 
> Other digest settings is
> 
> nondigestable = True
> scrub_nondigest = False
> digestable = True
> digest_is_default = 1
> mime_is_default_digest = 0
> digest_size_threshhold = 1
> digest_send_periodic = 1
> digest_volume_frequency = 3
> discard_these_nonmembers = (241 members)
> ban_list = (188 members)
> 
> The digest_size_threshhold = 1 may likely course the problem, but is 
> necessary as a digest containing a single mail is sent each time a mail is 
> sent to the list-address as suggested by 
> https://mail.python.org/pipermail/mailman-users/2014-August/077622.html.


That's a bug  which was
fixed in MM 2.1.16, but in any case, if you don't want digests triggered
on size and your mailman is older than 2.1.16, setting
digest_size_threshhold = 1 (KB = 10 MB) should stop digests being
triggered on size unless your list has a lot of large graphics attached
to posts. I.e. 10MB / 100 posts is still 100KB per post.


Anyway, I understood your OP to say digests were being sent only weekly
when batches of held messages are approved. If as you say,
digest_send_periodic =Yes and /usr/lib/mailman/cron/senddigests is run
by cron every day at noon, even if 50 messages are approved and 30 of
them are sent immediately in a digest (triggered on size), the other 20
should be sent in a digest the next noon.

If this is not the case, either cron/senddigests is not running every
noon or it is somehow skipping this list or encountering errors with
this list. Is there anything in Mailman's error log?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] 64 bit encoding

[Mark Sapiro]

On 11/03/2015 06:42 PM, Ruben Safir wrote:
> I'm converting my mailing lists from majordomo to mailman using postfix.
>  A lot of little issues have cropped up but the biggest problem I have
> currently is that it seems that mailman is converting files to 64 bit
> which is screwing up my home cooked archives but good.


Actually, Mailman is sending messages in UTF-8 character set as base64
encoded. Actually, many MUAs will also base64 encode UTF-8 message bodies.

This is actually a python email library thing. You can change the
encoding for UTF-8 message bodies with the following patch to
Mailman/Message.py, but if your messages are not predominately ascii
text, you won't like the result any better.

diff -u 2.1/Mailman/Message.py 21/Mailman/Message.py
--- 2.1/Mailman/Message.py  2014-05-17 18:34:20.240159000 -0700
+++ 21/Mailman/Message.py   2015-11-04 08:50:31.772899979 -0800
@@ -36,6 +36,10 @@
 from Mailman import mm_cfg
 from Mailman import Utils

+email.Charset.add_charset('utf-8',
+  email.Charset.SHORTEST,
+  email.Charset.QP,
+  'utf-8')
 COMMASPACE = ', '

 mo = re.match(r'([\d.]+)', email.__version__)

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] 64 bit encoding

[Mark Sapiro]

On 11/04/2015 09:16 AM, Ruben Safir wrote:
> 
> Oh thank you!  Because I was reading that it is triggered by header
> msg_header or msg_footer, but nobody really know what that was exactly.
>  It didn't match any settings in the interface.  I greatly appreciate this


To be more specific, if a list specifies a msg_header and/or a
msg_footer (in the list admin Non-digest options), Mailman will decode
the message body of a text/plain message in order to prepend the
msg_header and/or append the msg_footer. Then the message body is
re-encoded by the email library when Mailman sets the new body.

Thus, if msg_header and msg_footer are both empty, the recoding won't
happen, but when it does, it is controlled by the
email.Charset.add_charset() settings for the character set of the body,
and the patch I gave you changes the body encoding from base64 to
quoted-printable.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] 64 bit encoding

[Ruben Safir]

On 11/04/2015 12:10 PM, Mark Sapiro wrote:
>  You can change the
> encoding for UTF-8 message bodies with the following patch to
> Mailman/Message.py, but if your messages are not predominate


Oh thank you!  Because I was reading that it is triggered by header
msg_header or msg_footer, but nobody really know what that was exactly.
 It didn't match any settings in the interface.  I greatly appreciate this

Ruben
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org