Re: [Mailman-Users] Mailman digest issues
Further info on the problem is that the list admin just released 47 mails 30 minutes ago (please note that the digest_size_threshhold is now = 0, was previously 1000). Until now the list have sent 22 digest-mails with a single mail in each digest mail, all named Volume 20, but with increasing Issue number from 1 to 22. The numbering is expected, but the mails should've been send as a collection, not as individual mails.
Right now the settings are
nondigestable = True scrub_nondigest = False digestable = True digest_is_default = 1 mime_is_default_digest = 0 digest_size_threshhold = 0 digest_send_periodic = 1 digest_header = '' digest_volume_frequency = 3
There is no /var/lib/mailman/lists/LISTNAME/digest.mbox for the list in question, or any other list. Though I don't know which other lists do send digest mails.
The list admin now have Emergency-moderated the list. I guess this is just to stop all incoming traffic from being sent out, and have no effect on what the list admin do release, right?
Henrik Rasmussen
-----Oprindelig meddelelse----- Fra: Henrik Rasmussen Sendt: 12. august 2014 09:32 Til: Mark Sapiro; mailman-users@python.org Emne: SV: [Mailman-Users] Mailman digest issues
On 08/12/2014 03:00 AM, Mark Sapiro wrote:
On 08/11/2014 06:15 AM, Henrik Rasmussen wrote:
I am using Mailman version 2.1.12.
But he also complains that no digest mails are being sent when he set _send_digest_now to Yes. Did he press "Submit Your Changes" after setting _send_digest_now to Yes? If so, and if there were digested messages and digest members with delivery enabled, something else is wrong.
Yes he did. I did too, afterwards.
What response did he get when pressing "Submit Your Changes" after setting _send_digest_now to Yes? What's in Mailman's error log.
I got the message "There was no digest to send". No messages regarding this list in /var/log/mailman/error (or any other log in this directory for that matter).
The smtp log show that the list do send message (to normal-members I guess), but I can't verify if messages are sent to digest-members. The list admin say no mails are sent to digest-members.
He also set digest_send_periodic to Yes.
We're confused that the digest_send_periodic text is saying "Should a digest be dispatched daily when the size threshold isn't reached?" as he wants the digest to be sent weekly as set in digest_volume_frequency. digest_volume_frequency has nothing to do with how often periodic digests are sent. It only controls how often the vvv is incremented and ii is reset in the "List_name Digest, Vol vvv, Issue ii" >Subject: header of the digest.
I am still confused, even after reading section 2.6 in http://www.gnu.org/software/mailman/mailman-admin.pdf. In my understanding, (and I know I'm wrong here) if the volume number is changed weekly, but digest mails are sent daily, all digests will contain the same volume number all week long. What is the difference between volume number and issue number, and when do Mailman send what?
Where can I see if digest mails are in fact being sent out?
How can I tell normal from digest? Will the digest mails mention Digest I the SMTP log. If so, no digests have been sent.
Where will Mailman log digest issues?
No errors in the error log. Cron/senddigests -l LISTNAME. However, shows
[root@mailman.example.com]# /usr/lib/mailman/cron/senddigests -l Sci-diku-imageworld Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 106, in <module> main() File "/usr/lib/mailman/cron/senddigests", line 84, in main mlist = MailList.MailList(listname, lock=0) File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/usr/lib/mailman/Mailman/MailList.py", line 626, in Load raise Errors.MMUnknownListError Mailman.Errors.MMUnknownListError
Note, that often the output, if any, from Mailman's cron jobs is mailed to the 'mailman' user which happens to be the site list. If the site list is not configured to accept non-member posts, and the >site admin is not a member of the site list, this output is often lost. You can either set the site list as above or add a MAILTO= directive with a deliverable address to Mailman's crontab.
Thanks.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
Henrik Rasmussen
On 08/12/2014 03:11 AM, Henrik Rasmussen wrote:
Further info on the problem is that the list admin just released 47 mails 30 minutes ago (please note that the digest_size_threshhold is now = 0, was previously 1000). Until now the list have sent 22 digest-mails with a single mail in each digest mail, all named Volume 20, but with increasing Issue number from 1 to 22. The numbering is expected, but the mails should've been send as a collection, not as individual mails.
This is a bug <https://bugs.launchpad.net/mailman/+bug/558274>. It was fixed in 2.1.16. Prior to that, setting digest_size_threshhold = 0 would produce the behavior you see.
If you want no digests based on size in older versions, set digest_size_threshhold = a very large number.
There is no /var/lib/mailman/lists/LISTNAME/digest.mbox for the list in question, or any other list. Though I don't know which other lists do send digest mails.
Because the digest has been sent.
The list admin now have Emergency-moderated the list. I guess this is just to stop all incoming traffic from being sent out, and have no effect on what the list admin do release, right?
I don't understand this question. With emergency = Yes, all posts will be held and if approved by the list admin/moderator will be delivered to the list and accumulated for the digest (which with digest_size_threshhold = 0 pre 2.1.16 will be sent immediately, one digest per post).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Henrik Rasmussen -
Mark Sapiro