[Mailman-Users] Digest Mode

[Michael LaFarr]

Hello.  I am new to mailman.  I am working to set up the digest 
function.  I would like to set up a list that does not give the user the 
choice of how they will receive messages (individually or grouped).  I 
would like to configure the list so that when I approve incoming messages, 
all messages will all be sent grouped in one email rather than separate 
emails.  I can't seem to find a way to do that.  Any suggestions?
Thank you,
Michael LaFarr


Michael J. LaFarr
Assistant Director of Student Affairs
Harvard School of Public Health
677 Huntington Avenue, Kresge G-20
Boston, MA 02115
phone: 617.432.6650
fax: 617.432.3879 
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Digest mode.

[Kenneth G. Gordon]

One of my subscribers is complaining that he cannot activate the digest mode 
for his 
account. I can find nothing wrong in the admin database.

Where should I look for this problem?

Ken Gordon
--
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] Digest mode wish

[Ryan Hyma]

I think it would be extremely useful to be able to click on an index
entry at the top of the digest and have it take you down to the place in
the digest where that mail starts.  Some of my digests are very large
and I only care about a couple of the messages.  They can be very
cumbersome to find.

-Ryan



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

[Mailman-Users] digest mode links

[John Griessen]

Why do digest mode links rename a .jpg file?  A Mac OS X user can't see 
attachments.


URL: 

-- next part --
A non-text attachment was scrubbed...
Name: DSC04246.JPG
Type: application/octet-stream
Size: 153072 bytes
Desc: not available


Thanks,

John
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digest Mode

[Jim Tittsler]

On Aug 12, 2005, at 03:40, Michael LaFarr wrote:

> I would like to set up a list that does not give the user the
> choice of how they will receive messages (individually or grouped).  I
> would like to configure the list so that when I approve incoming  
> messages,
> all messages will all be sent grouped in one email rather than  
> separate
> emails.

As you've stated the problem, there isn't an existing automated way  
to do it.  Digests are typically configured to be sent periodically  
(by a cron job that by default runs once per day).

However, you could:
- set nondigestable=No on the non-digest options page to prevent  
users from subscribing to individual messages
- you may want to increase digest_size_threshold if you really want  
all approved messages to be in a single digest
- after you have approved the messages, manually run:
~mailman/cron/senddigests -l listname
to force the delivery of a digest at that time (or wait for the  
next cron-invoked digest sending)




-- 
Jim Tittsler http://www.OnJapan.net/  GPG: 0x01159DB6
Python Starship  http://Starship.Python.net/crew/jwt/
Mailman IRC  irc://irc.freenode.net/#mailman



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Digest mode.

[Mark Sapiro]

On 1/19/19 2:44 PM, Kenneth G. Gordon wrote:
> One of my subscribers is complaining that he cannot activate the digest mode 
> for his 
> account. I can find nothing wrong in the admin database.
> 
> Where should I look for this problem?


What does the user do and what happens?

-- 
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] digest mode links

[Mark Sapiro]

John Griessen wrote:

>Why do digest mode links rename a .jpg file?  A Mac OS X user can't see 
>attachments.
>
>
>URL: 
>
>-- next part --
>A non-text attachment was scrubbed...
>Name: DSC04246.JPG
>Type: application/octet-stream
>Size: 153072 bytes
>Desc: not available


Because in your installation, the scrubber generates the extension from
the Content-Type which in this case is application/octet-stream and
not image/jpeg as it should be for a JPEG file.

This is really an issue with the MUA that composed the message, but if
you want Mailman to use the extension from the file name rather than
one appropriate for the Content-Type, you can set

SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True

in mm_cfg.py.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest mode links

[LuKreme]

On 28-Feb-10 09:59, John Griessen wrote:

A non-text attachment was scrubbed...
Name: DSC04246.JPG
Type: application/octet-stream


Because it was defined incorrectly as an application/octet stream 
instead of as an image/jpeg



--
I draw the line at 7 unreturned phone calls.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest mode links

[LuKreme]

On 28-Feb-10 11:03, Mark Sapiro wrote:

SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True


Would that be considered unsafe?

I mean, it SEEMS unsafe, but is it really?

--
Overhead, without any fuss, the stars were going out.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest mode links

[Mark Sapiro]

LuKreme wrote:

>On 28-Feb-10 11:03, Mark Sapiro wrote:
>> SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True
>
>Would that be considered unsafe?
>
>I mean, it SEEMS unsafe, but is it really?


It could be. Suppose I send a message to your list with an attached
evil_app.exe file that I call Content-Type: text/plain without a
charset. This file now gets scrubbed stored on your server and is
accessable in your archives as a .exe file, so if someone retrieves it
and tries to open it, it will open as an executable.

If it were stored with an appropriate extension for its MIME type,
attempting to open it would probably try to open it with a text viewer
and just display garbage.

On the other hand, if you don't scrub_nondigest, it was already
delivered to your list's message and MIME digest members with it's
original file name and extension, and this has no effect on that, and
that's probably the more serious risk.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Digest mode bug in 2.1b2

[Peter Bengtson]

Mailman 2.1b2 allows subscribers to select digest delivery mode - even
if the list is set up not to deliver digests at all. What happens then
is that these subscribers do not get any mail at all. The admin is not
informed, but when the list of subscribers is browsed, he is informed
that "there are certain subscribers who will not receive any mail", but
not who these are, which means that he has to go through the entire
roster by hand to find them. In my case, a list of 2600 subscribers.

This has to be regarded as a severe bug.

Why is it possible to select digest mode at all for a list which doesn't
have digests enabled?

/ Peter Bengtson


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] Digest mode bug in 2.1b2

[Peter Bengtson]

> For your specific question, this is not a bug, Mailman is not just
> another out of the box, ready to go, software; there are many ways
> to customize it, but you have failed complete your customization. 

I must say that your answer is a bit surprising. Mailman offers an
enormous wealth of features that are intended to ease the task of
customisation or make customisation unnecessary. I am aware of the HTML
templates and have modified them - yet, it is still possible to switch
on digest mode through e-mail commands. Moreover, the templates have to
be re-edited each time a new Mailman version appears.

> Although a few of your subscribers may send a help command to
> the robot, and receive the command list, if you include the notice,
> and they send a digest command anyway, then it's their fault for 
> not reading your new custonized documentation. 

Clearly, if it is possible to switch on a feature no matter what the
administrator selects in the configuration sections, and the feature
produces unwanted behaviour - in this case, the total suppression of all
mail, *without* the subscriber or the administrator ever getting to know
about it, then it is clearly and obviously a bug. Particularly as it is
completely impossible for the administrator to find out which subscriber
is affected, but has to go through each and every one. 

Mailman is fantastic, and superior to all other mailing list software
I've seen - I love it to bits - but in this respect it falls down
miserably. Please: trying to pass this obvious bug off as an
uncustomised list configuration issue is a bit ... well, you know.
Especially since configuring the HTML pages (safety by obscurity) still
allows the user to select digest mode by e-mail.

As a software engineer I know that chanches are about 95% that this bug
is easy to fix. 

/ Peter Bengtson


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] digest-mode not functioning properly

[Lluis Montoliu]

Dear listers,
Suddenly, some users of two mailman (version 2.1.11) lists I am 
administering have started to complain about digest-mode not functioning 
properly. In brief, messages are not being sent in digest-mode. Settings 
are 1024 Kb for size before sending a digest message or daily, if this 
size isn't reached, new digest volumes should be started daily too. No 
messages sent. I have tried to trigger the "immediate sending 
digest-mode" from administration settings (Should Mailman send the next 
digest right now, if it is not empty?) and no way, nothing happened. I 
even tried myself, registering one of my email addresses a couple of 
days ago and setting this to digest-mode (normally I don't use this 
mode) and nothing, does not work.
It looks as if digest-mode stopped working for good. However, standard 
mode works fine. I have contacted my hosting provider and I am currently 
awaiting their response, but I decided to share this unexpected troubles 
in this forum, in case someone has seen it before and there is something 
I could do from the administrative interface.

Thanks for your comments.
Lluis
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Digest mode sending individual emails

[ml lists]

Hello,

I am having some problems with a mailman list that i administer.   The list
is configured to send digest emails once a week (via the web ui) but this
is not happening, instead emails are being sent individually, as they are
posted to the list, but tagged as digest.

Would anyone have any suggestion how to fix this so they are sent weekly?

I'm running Ubuntu 11.10 and mailman 2.1.14-1
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digest mode bug in 2.1b2

[Support Desk]

Many admin settings and details are here: 
http://www.imsa.edu/~ckolar/mailman/mailman-administration-v2.html 

For your specific question, this is not a bug, Mailman is not just
another out of the box, ready to go, software; there are many ways
to customize it, but you have failed complete your customization. 

Edit your list information pages to remove those links you do not
want YOUR subscribers to use: 
http://YOUR_SERVER/mailman/edithtml/YOUR_LIST 
which is accessable through your admin panel, contains "options" 
http://YOUR_SERVER/mailman/edithtml/YOUR_LIST/options.html
remove or  the digest button and mime/plaintext
options rows, and any other options you have disabled. 

You may wish to include a notice on list info page, and in footer or 
header informing subscribers that NO digest is available, although, 
some would question whether this is wise, it IS your list, to run the 
way you see fit. 

Although a few of your subscribers may send a help command to
the robot, and receive the command list, if you include the notice,
and they send a digest command anyway, then it's their fault for 
not reading your new custonized documentation. 

SD 

- Original Message - 
From: "Peter Bengtson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 25, 2002 3:03 AM
Subject: [Mailman-Users] Digest mode bug in 2.1b2


| Mailman 2.1b2 allows subscribers to select digest delivery mode - even
| if the list is set up not to deliver digests at all. What happens then
| is that these subscribers do not get any mail at all. The admin is not
| informed, but when the list of subscribers is browsed, he is informed
| that "there are certain subscribers who will not receive any mail", but
| not who these are, which means that he has to go through the entire
| roster by hand to find them. In my case, a list of 2600 subscribers.
| 
| This has to be regarded as a severe bug.
| 
| Why is it possible to select digest mode at all for a list which doesn't
| have digests enabled?
| 
| / Peter Bengtson
| 
| 
ŠYšK®ÉšŠX§‚X¬´Æ¢–f§RÇ«²œ­†‰è®m¶Ÿÿ™¨¥§+a¢z+ƒùšŠYšŸùb²Ø§~æj)fj{¬z»j)fjq@Bm§ÿðÃ
r¶'¢¸?r›Šßj¬&šœ

Re: [Mailman-Users] digest-mode not functioning properly

[Lluis Montoliu]

Some more data. Hosting provider can't find anything wrong. I have set  
a new list, fake users for testing purposes. Set one of them for  
standard the other for digest-mode and played with size limits and  
daily and everything worked as expected, in this test list, whereas  
the two large list are not sending any digest-mode, with the exact  
same settings, even if I decrease the value to 256 or if I trigger  
sending a new digest dispatch right now, which does not happen. I'm  
totally amazed. I've seen the archives of mailman and, unfortunately,  
the problems with digest-mode appear to be rather common, many reports  
found, but not really solutions, at least, I could not find the one  
that will fix my bug.

Thanks again for your help and suggestions

Lluis


Quoting Lluis Montoliu :


Dear listers,
Suddenly, some users of two mailman (version 2.1.11) lists I am  
administering have started to complain about digest-mode not  
functioning properly. In brief, messages are not being sent in  
digest-mode. Settings are 1024 Kb for size before sending a digest  
message or daily, if this size isn't reached, new digest volumes  
should be started daily too. No messages sent. I have tried to  
trigger the "immediate sending digest-mode" from administration  
settings (Should Mailman send the next digest right now, if it is  
not empty?) and no way, nothing happened. I even tried myself,  
registering one of my email addresses a couple of days ago and  
setting this to digest-mode (normally I don't use this mode) and  
nothing, does not work.
It looks as if digest-mode stopped working for good. However,  
standard mode works fine. I have contacted my hosting provider and I  
am currently awaiting their response, but I decided to share this  
unexpected troubles in this forum, in case someone has seen it  
before and there is something I could do from the administrative  
interface.

Thanks for your comments.
Lluis







--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly

[Mark Sapiro]

Lluis Montoliu wrote:

>the two large list are not sending any digest-mode, with the exact  
>same settings, even if I decrease the value to 256 or if I trigger  
>sending a new digest dispatch right now, which does not happen. I'm  
>totally amazed. I've seen the archives of mailman and, unfortunately,  
>the problems with digest-mode appear to be rather common, many reports  
>found, but not really solutions, at least, I could not find the one  
>that will fix my bug.


There is almost certainly a message or messages in the
lists/LISTNAME/digest.mbox files for these lists that is causing an
exception to be thrown in the scrubber in it's attempt to process the
digest.

Ask the hosting provider to look for relevant error messages and
tracebacks in Mailman's error log.

You may have to have the hosting provider just move the
lists/LISTNAME/digest.mbox files aside and abandon the current
accumulated digests if the hosting provider can't do anything more
selective to find and fix the offending messages.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly

[Lluis Montoliu]

Dear Mark, dear listers,

I responded much too quickly that the issues with digest-mode were  
fixed. In reality they are not fixed, they reproduced and it is being  
a pain. In collaboration with our host, we have cleared, several  
times, the buffer, discarding repeteadly volumes (to get rid of  
potentially offending messages), reinitiate the mailman several times  
(in case it would be frozen somehow) and, still, is not sending any  
volume daily or when it reaches 250 kb, as it should, according to  
current settings. We have set new lists in the server and they seem to  
work normally, distributing volumes daily, as they should. The  
problems seems to be associated with these two lists, one with 600  
other with 1700 registered members. Most of the 600 email addresses  
are also represented in the 1700 ones.


The only way we found it can work is by triggering, daily, manually,  
from administrative panel, the distribution of a new volume digest, if  
it is not empty. This works, nicely, and the digests are distributed  
normally and do not appear to have any problem. Of course, as you can  
imagine, this is suboptimal and it is not an acceptable solution.


Even though we use a dedicated web server this is administered by host  
and, thus, we have no root privileges and our administrator, at the  
hosting, is not able to provide any additional help beyond clearing  
volumes or reinitiating mailman nor it would allow us to access the  
mailman folder to explore for any additional problems. The found an  
email address they thought was causing some problems, although it is a  
standard email address used normally by his owner outside mailman  
context. Nonetheless we removed this address, but problems continued.  
Could it be that we have still, somewhere, an email address, someone  
that is registered in both lists for digest mode, triggering these  
troubles and limiting the distribution of volumes?


At hosting level they keep indicating that mailman is outdated, no  
longer maintained and that we should consider moving to other  
programs, like phplists, which I checked and doesn't do, at all, the  
same function as mailman. Phplist is for newsletter distributions not  
for email-based discussions, as mailman does nicely.


I'm happy with mailman, and I'd like to keep using it but when I come  
across these troubles, like now, where it seems nothing can be done to  
fix this no-digest-volume-dispatching it is really disappointing.


What else could I do? Thanks again for ideas or suggestions.

best regards

Lluis



Quoting Mark Sapiro :


Lluis Montoliu wrote:


the two large list are not sending any digest-mode, with the exact
same settings, even if I decrease the value to 256 or if I trigger
sending a new digest dispatch right now, which does not happen. I'm
totally amazed. I've seen the archives of mailman and, unfortunately,
the problems with digest-mode appear to be rather common, many reports
found, but not really solutions, at least, I could not find the one
that will fix my bug.



There is almost certainly a message or messages in the
lists/LISTNAME/digest.mbox files for these lists that is causing an
exception to be thrown in the scrubber in it's attempt to process the
digest.

Ask the hosting provider to look for relevant error messages and
tracebacks in Mailman's error log.

You may have to have the hosting provider just move the
lists/LISTNAME/digest.mbox files aside and abandon the current
accumulated digests if the hosting provider can't do anything more
selective to find and fix the offending messages.

--
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly

[Stephen J. Turnbull]

Lluis Montoliu writes:

 > At hosting level they keep indicating that mailman is outdated, no  
 > longer maintained and that we should consider moving to other  
 > programs

Your hosting service is either really failing to do their homework, or
outright lying to you.  Mailman is very much maintained, although
21.1.14 is *very* stable, so almost all development activity is on
Mailman 3.  You should consider moving to a more honest and competent
service.

 > >> the problems with digest-mode appear to be rather common, many reports
 > >> found, but not really solutions, at least, I could not find the one
 > >> that will fix my bug.

Problems with digest mode that I can remember in about a decade of
Mailman use and participation in these lists (and *never* experienced
personally! just seen on the lists) generally are problems with the
digest messages themselves, and the fact that Windows mail clients
often do a horrible job of handling them.  As far as I can remember,
problems with collecting and sending digests are pretty rare, and
usually due to misconfiguration.  Such problems are usually quickly
resolved if the Mailman admin has root.

The principal cause of *ongoing* problems is that the Mailman admin
doesn't have root, and the hosting service is either unable or
unwilling to configure Mailman properly.

Sorry I cannot be of more immediate help, but it really angers me that
so many hosting services offer Mailman, and then turn around and
cripple it with lack of support.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly

[Lluis Montoliu]

Thanks for support Stephen. I'm using version 2.1.11 and you've got it  
right. Our main problem is lack of access at root level, therefore we  
are limited to what we can do through the mailman admin panel and to  
suggest our hosting service to do this or that, which they can choose  
to do or not.


The fact that two of my lists are experiencing these problems and not  
the rest suggest me that some email addresses that could be shared  
among the two could be the culprit. I'm investigating this.


And, yes Windows-email clients can result in unexpected consequences.  
Also, heavily formatted messages, with complex signatures and graphics  
embedded. We recently discovered messages were either filtered or  
blocking the list because of that.


Currently, problems can't be related to digest messages themselves,  
because when I trigger their distribution, manually, from admin panel,  
they are indeed distributed. Simply they are not distributed daily, or  
when they reach 256 kb, as current settings indicate and sort of keep  
accummulating messages in an endless manner.


Very intriguing

Lluis





Quoting "Stephen J. Turnbull" :


Lluis Montoliu writes:

 > At hosting level they keep indicating that mailman is outdated, no
 > longer maintained and that we should consider moving to other
 > programs

Your hosting service is either really failing to do their homework, or
outright lying to you.  Mailman is very much maintained, although
21.1.14 is *very* stable, so almost all development activity is on
Mailman 3.  You should consider moving to a more honest and competent
service.

 > >> the problems with digest-mode appear to be rather common, many reports
 > >> found, but not really solutions, at least, I could not find the one
 > >> that will fix my bug.

Problems with digest mode that I can remember in about a decade of
Mailman use and participation in these lists (and *never* experienced
personally! just seen on the lists) generally are problems with the
digest messages themselves, and the fact that Windows mail clients
often do a horrible job of handling them.  As far as I can remember,
problems with collecting and sending digests are pretty rare, and
usually due to misconfiguration.  Such problems are usually quickly
resolved if the Mailman admin has root.

The principal cause of *ongoing* problems is that the Mailman admin
doesn't have root, and the hosting service is either unable or
unwilling to configure Mailman properly.

Sorry I cannot be of more immediate help, but it really angers me that
so many hosting services offer Mailman, and then turn around and
cripple it with lack of support.




--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly

[Mark Sapiro]

Lluis Montoliu wrote:
>
>The fact that two of my lists are experiencing these problems and not  
>the rest suggest me that some email addresses that could be shared  
>among the two could be the culprit. I'm investigating this.


This doesn't seem likely.


>Currently, problems can't be related to digest messages themselves,  
>because when I trigger their distribution, manually, from admin panel,  
>they are indeed distributed. Simply they are not distributed daily, or  
>when they reach 256 kb, as current settings indicate and sort of keep  
>accummulating messages in an endless manner.


It is difficult to imagine what could be causing this. Digests are
working as expected for some lists so cron/senddigests is running.
Digests can be sent manually from the web admin GUI for the affected
lists only they are not sent periodically (via cron/senddigests) or
when triggered on size. This is very mysterious.

You could try to go to the web admin Digest options page for the
affected lists and set digestable to No and Submit Your Changes. This
will produce a warning about digest members not receiving mail which
you can ignore. Then set digestable back to Yes and Submit Your
Changes again. This entire process should have no net effect, but it
may clear some strange condition if there is one.

It is unfortunate that the hosting service isn't more interested. They
say Mailman is outdated, yet there are releases from 2.1.12 through
2.1.14 that are significantly newer than the 2.1.11 release they are
running. In any case, if you could get them to look at Mailman's error
log to see if there are any errors related to these digests, maybe we
could figure out what's going on.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly

[Lluis Montoliu]

Thanks Mark, just tried what you suggested, and toggled off and back  
on the digestable options. Will see how it goes on the next couple of  
days, whether digest will be dispatched automatically or not.


Found only 13 addresses shared by the two lists from users that had  
selected digest-mode. None of these addresses is associated with  
bounces or known unexpected behaviour, therefore you are probably  
right, and these are not the cause.


In addition, will try convincing my hosting to upgrade our mailman  
installation to 2.1.14. Will let you know.


Lluis



Quoting Mark Sapiro :


Lluis Montoliu wrote:


The fact that two of my lists are experiencing these problems and not
the rest suggest me that some email addresses that could be shared
among the two could be the culprit. I'm investigating this.



This doesn't seem likely.



Currently, problems can't be related to digest messages themselves,
because when I trigger their distribution, manually, from admin panel,
they are indeed distributed. Simply they are not distributed daily, or
when they reach 256 kb, as current settings indicate and sort of keep
accummulating messages in an endless manner.



It is difficult to imagine what could be causing this. Digests are
working as expected for some lists so cron/senddigests is running.
Digests can be sent manually from the web admin GUI for the affected
lists only they are not sent periodically (via cron/senddigests) or
when triggered on size. This is very mysterious.

You could try to go to the web admin Digest options page for the
affected lists and set digestable to No and Submit Your Changes. This
will produce a warning about digest members not receiving mail which
you can ignore. Then set digestable back to Yes and Submit Your
Changes again. This entire process should have no net effect, but it
may clear some strange condition if there is one.

It is unfortunate that the hosting service isn't more interested. They
say Mailman is outdated, yet there are releases from 2.1.12 through
2.1.14 that are significantly newer than the 2.1.11 release they are
running. In any case, if you could get them to look at Mailman's error
log to see if there are any errors related to these digests, maybe we
could figure out what's going on.

--
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digest mode sending individual emails

[Mark Sapiro]

ml lists wrote:
>
>I am having some problems with a mailman list that i administer.   The list
>is configured to send digest emails once a week (via the web ui)


Lists can be configured to send digests periodically
(digest_send_periodic = Yes), but the frequency is determined by how
often Mailman's cron/senddigests runs.


>but this
>is not happening, instead emails are being sent individually, as they are
>posted to the list, but tagged as digest.


You have probably set digest_size_threshhold to 0 thinking this means
unlimited instead of 'send a digest with every post'. See the current
doc at  and the bug
report at .

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digest mode sending individual emails

[ml lists]

On 13 March 2013 22:56, Mark Sapiro  wrote:
>
> Lists can be configured to send digests periodically
> (digest_send_periodic = Yes), but the frequency is determined by how
> often Mailman's cron/senddigests runs.
>
> You have probably set digest_size_threshhold to 0 thinking this means
> unlimited instead of 'send a digest with every post'. See the current
> doc at  and the bug
> report at .

I had/have the following
digest_size_threshhold = 30
digest_send_periodic = no
digest_volume_frequency = weekly

And if I understood correctly, this regardless of threshhold size
should only send weekly, no?

With "cron/senddigests"  should there be a crontab entry on the system
for this or is it controlled elsewhere?
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digest mode sending individual emails

[Mark Sapiro]

ml lists wrote:
>
>I had/have the following
>digest_size_threshhold = 30
>digest_send_periodic = no
>digest_volume_frequency = weekly
>
>And if I understood correctly, this regardless of threshhold size
>should only send weekly, no?


No. This will send a digest whenever the size reaches about 30K bytes
and only then. If posts to the list are large, I.e. greater than about
30K, this will send a digest for each post.

Periodic digests will not be sent.

Digest volume frequency has nothing to do with when digests are sent.
It controls how often the Vol number in the Subject line "LISTNAME
Digest, Vol ##, Issue ##" is incremented and the Issue number reset to
1.


>With "cron/senddigests"  should there be a crontab entry on the system
>for this or is it controlled elsewhere?


There should be a crontab for mailman that runs several jobs. Depending
on how Mailman was installed, this may be a system crontab, e.g.,
/etc/cron.d/mailman, or the Mailman user's crontab, e.g.,
/var/spool/cron/mailman.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Digest mode attachment URL is bad

[Larry McMahon-Padolski]

Hi,
When a user attaches a non-txt file, Mailman provides a URL pointing to  
the attachment.
This seems only to apply to digest mode.

For example:
/pipermail/test_domain.com/attachments/20050201/d8f9df80/ReneeSUMMERSCOURSESCAPP.doc
However the proper URL is:
http://www.domain.com/pipermail/test_domain.com/attachments/20050201/d8f9df80/ReneeSUMMERSCOURSESCAPP.doc
Is this the fix?
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp
Regards,
Larry


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Digest mode attachment URL is bad

[Mark Sapiro]

Larry McMahon-Padolski wrote:
>
>When a user attaches a non-txt file, Mailman provides a URL pointing to  
>the attachment.
>This seems only to apply to digest mode.
>
>For example:
>/pipermail/test_domain.com/attachments/20050201/d8f9df80/ReneeSUMMERSCOURSESCAPP.doc
>
>However the proper URL is:
>http://www.domain.com/pipermail/test_domain.com/attachments/20050201/d8f9df80/ReneeSUMMERSCOURSESCAPP.doc
>
>Is this the fix?
>http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp

Probably. Make sure you read the part about existing lists and fix_url.

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] digest-mode not functioning properly (issued fixed!)

[Lluis Montoliu]

Dear Mark,
excellent suggestion, indeed there were messages heavily formatted  
which apparently affected mailman and its normal processing of digest  
buffer. There was no need to remove these messages. Re-starting the  
list server did the miracle and both lists are now working fine,  
dispatching the digest-mode messages as intended. Thanks again for  
your help. Issue fixed and closed.

regards
Lluis



Quoting Mark Sapiro :


Lluis Montoliu wrote:


the two large list are not sending any digest-mode, with the exact
same settings, even if I decrease the value to 256 or if I trigger
sending a new digest dispatch right now, which does not happen. I'm
totally amazed. I've seen the archives of mailman and, unfortunately,
the problems with digest-mode appear to be rather common, many reports
found, but not really solutions, at least, I could not find the one
that will fix my bug.



There is almost certainly a message or messages in the
lists/LISTNAME/digest.mbox files for these lists that is causing an
exception to be thrown in the scrubber in it's attempt to process the
digest.

Ask the hosting provider to look for relevant error messages and
tracebacks in Mailman's error log.

You may have to have the hosting provider just move the
lists/LISTNAME/digest.mbox files aside and abandon the current
accumulated digests if the hosting provider can't do anything more
selective to find and fix the offending messages.

--
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org