Re: [Mailman-Users] Disallow digest, but getting warning

[Mark Sapiro]

On 4/14/2011 4:40 AM, Ralf Hildebrandt wrote:
>>
>> I patched mailman to emit that info.
>> m(
> 
> --- /usr/src/mailman-2.1.14/Mailman/Cgi/admin.py  2010-12-02 
> 08:41:27.0 +0100
> +++ /usr/src/mailman-2.1.14/Mailman/Cgi/admin.py  2011-04-14 
> 13:34:53.533844622 +0200
> @@ -189,11 +189,15 @@
>  _('''You have digest members, but digests are turned
>  off. Those people will not receive mail.'''),
>  tag=_('Warning: '))
> +doc.addError(mlist.getDigestMemberKeys(),
> +tag=_('Warning: '))
>  if not mlist.nondigestable and mlist.getRegularMemberKeys():
>  doc.addError(
>  _('''You have regular list members but non-digestified mail 
> is
>  turned off.  They will receive non-digestified mail until you
>  fix this problem.'''), tag=_('Warning: '))
> +doc.addError(mlist.getRegularMemberKeys(),
> +tag=_('Warning: '))
>  # Glom up the results page and print it out
>  show_results(mlist, doc, category, subcat, cgidata)
>  print doc.Format()


See . My patch is a bit
different, see attached, but the intent is the same.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

=== modified file 'Mailman/Cgi/admin.py'
--- Mailman/Cgi/admin.py2010-09-10 22:17:01 +
+++ Mailman/Cgi/admin.py2011-04-14 23:07:45 +
@@ -187,13 +187,15 @@
 if not mlist.digestable and mlist.getDigestMemberKeys():
 doc.addError(
 _('''You have digest members, but digests are turned
-off. Those people will not receive mail.'''),
+off. Those people will not receive mail.
+Affected member(s) %r.''' % mlist.getDigestMemberKeys()),
 tag=_('Warning: '))
 if not mlist.nondigestable and mlist.getRegularMemberKeys():
 doc.addError(
 _('''You have regular list members but non-digestified mail is
 turned off.  They will receive non-digestified mail until you
-fix this problem.'''), tag=_('Warning: '))
+fix this problem. Affected member(s) %r.''' %
+mlist.getRegularMemberKeys()), tag=_('Warning: '))
 # Glom up the results page and print it out
 show_results(mlist, doc, category, subcat, cgidata)
 print doc.Format()

--
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] TypeError: cannot concatenate 'str' and 'NoneType'objects

[Mark Sapiro]

Jesus Cea wrote:
>
>This morning I received this:
>
>"""
>Your "cron" job on stargate
>/usr/local/bin/python2.5 -S /home/mailman/cron/disabled
>
>produced the following output:
>
>Traceback (most recent call last):
>  File "/home/mailman/cron/disabled", line 224, in 
>main()
>  File "/home/mailman/cron/disabled", line 208, in main
>mlist.sendNextNotification(member)
>  File "/home/mailman/Mailman/Bouncer.py", line 280, in sendNextNotification
>msg['Subject'] = 'confirm ' + info.cookie
>TypeError: cannot concatenate 'str' and 'NoneType' objects
>"""
>
>The problem is, the particular user is marked as "disabled delivery",
>but its bounce information is not the responsible for that:
>
>"""
 m.getDeliveryStatus("X")
>4
 m.bounce_info["X"]
>current score: 1.0
>last bounce date: (2011, 4, 13)
>email notices left: 7
>last notice date: (1970, 1, 2)
>confirmation cookie: None
>>
>"""
>
>So the delivery is disabled because "bounce", but the bounce score is
>too low for it (my threshold is 5.0).


I do not see any way in standard GNU Mailman that a user can be
disabled "BYBOUNCE" without appropriate bounce info.

Is your mailman installed from source or a distributer package? Do you
have any local patches? Do you run any local processes?


>When the "cron" executes "disabled" to send out the reminders, it tries
>to send to this user, but the process fails because the user is marked
>as "bounce" but no confirmation cookie is available.
>
>So, the process dies. No more notifications mails are send. PANIC! :).


Correct.


>I think I can solve this particular case, for a while, doing
>"m.setDeliveryStatus("X", 0)". But I will wait a couple of days, just in
>case you want me to do any kind of test.
>
>Checking the logs, I see this: (email and listname not shown)
>
>"""
>bounce:Apr 13 09:17:59 2011 (1567) list: X bounce score: 1.0
>bounce:Apr 13 13:56:29 2011 (5194) list: X already scored a bounce for
>date 13-Apr-2011
>bounce:Apr 14 09:00:03 2011 (24248) Notifying disabled member X for
>list: list
>bounce:Apr 14 12:05:16 2011 (12355) Notifying disabled member X for
>list: list
>bounce:Apr 14 12:06:21 2011 (12546) Notifying disabled member X for
>list: list
>bounce:Apr 14 12:17:09 2011 (14017) list: X residual bounce received
>bounce:Apr 14 13:31:00 2011 (20518) Notifying disabled member X for
>list: list
>bounce:Apr 14 13:31:15 2011 (20554) Notifying disabled member X for
>list: list
>"""


What are the other entries timestamped at or close to Apr 13 09:17:59
2011?

What are the processes with PIDs 1567, 5194 and 14017? These should all
be BounceRunner or perhaps OutgoingRunner if there are also entries in
Mailman's smtp-failure log. Are you running multiple sliced qrunners
or are qrunners being restarted.

See the FAQ at http://wiki.list.org/x/_4A9 for information on
completely stopping Mailman and all qrunners. Then stop Mailman and
all the runners and after everything is stopped, start Mailman just
once.

That may help if there are multiple copies of qrunners processing the
same slices.


>So here we have mailman getting a bounce for the address yesterday, and
>the original "notification" try and my subsequent tests, today.
>
>Hipotesis: The user set "disable delivery" but we have some bounces
>coming back, so the "disable delivery" sets by user is mutated
>incorrectly to "user bouncing", causing this problem.


I don't see how that can happen. When a bounce is received for a member
whose delivery is disabled for any reason, we just log the 'residual
bounce received' message and otherwise ignore it.


>Some more data:
>
>"""
 m.getDeliveryStatusChangeTime("X")
>1302776230.914567
 import time
 time.ctime(1302776230.914567)
>'Thu Apr 14 12:17:10 2011'
 m.getDeliveryStatus("X")
>4
>"""
>
>The change date, is consistent with this line on my log:
>
>"""
>bounce:Apr 14 12:17:09 2011 (14017) list: X residual bounce received
>"""


Yes, and that is very curious, but the member's delivery was already
disabled at 09:00, and unless the cron/disabled command in Mailman's
crontab has some options to process other than disabled BYBOUNCE
members, the member was already disabled BYBOUNCE at that time.

bounce:Apr 14 09:00:03 2011 (24248) Notifying disabled member X for
list: list

Also, a residual bounce does not change or update
DeliveryStatusChangeTime at least with standard Bouncer.py and Old
Style Memberships.py.


>This happens from time to time, and it is really painful, since others
>users are not getting their reminders, or they are getting them too late
>and their token has already expired.
>
>I will keep this state for a couple of days, just in case you need some
>more info. Then, I will clean it up. But this is a recurrent issue,
>happens from time to time.


You could always patch cron/disabled by finding this:


try:
mlist.sendNextNotification(member)
except Errors.NotAMemberError:
 

Re: [Mailman-Users] Problem with bounce_matching_headers

[Mark Sapiro]

Richard Damon wrote:
>
>Doesn't . only match a single character? I use filters more like
>
>Subject: .*remove.*
>
>so the .* matches any number of characters between the Subject header 
>and the word.

bounce_matching_headers is different from header_filter_rules. For
header_filter_rules, you might want something like

 ^Subject:.*remove

because the search is against all of the message's headers.

For bounce_matching_headers,

  Subject: .remove.

says search the subject header value for the pattern '.remove.' which
ought to succeed unless 'remove is at the very beginning or end of the
header.

-- 
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] Problem with bounce_matching_headers

[Richard Damon]

On 4/14/11 3:12 PM, Barry Finkel wrote:

I am running 2.1.14, and we had a problem where a list owner
subscribed a number of persons to a list, and many of these
persons want to be unsubscribed.  To catch mail directed
toward the list:

 Subject: Please remove me from your list

I added a line to bounce_matching_headers

 Subject: .remove.

(I placed it at the end of the Mailman-supplied lines),
and the next mail with that subject line was sent to the
list moderators.  Another mail message arrived:

 Subject: Again... Please remove me from this list

but this one was not diverted to the moderators.  What is
wrong with my bounce_matching_headers line?  Thanks.


Doesn't . only match a single character? I use filters more like

Subject: .*remove.*

so the .* matches any number of characters between the Subject header 
and the word.
This filter likely will have false positives, you may want something 
more like


Subject: .*remove.*list.*

--
Richard Damon

--
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] Problem with bounce_matching_headers

[Mark Sapiro]

Barry Finkel wrote
>
>I added a line to bounce_matching_headers
>
>  Subject: .remove.


I don't know why this didn't work unless it contains trailing
whitespace (leading whitespace is removed before matching). However,
if you are trying to match the 'word' remove, I would use

   Subject: \Wremove\W

See 

Note that bounce_matching_headers (and header_filter_rules) are matched
case insensitively.

-- 
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] Problem with bounce_matching_headers

[Barry Finkel]

I am running 2.1.14, and we had a problem where a list owner
subscribed a number of persons to a list, and many of these
persons want to be unsubscribed.  To catch mail directed
toward the list:

 Subject: Please remove me from your list

I added a line to bounce_matching_headers

 Subject: .remove.

(I placed it at the end of the Mailman-supplied lines),
and the next mail with that subject line was sent to the
list moderators.  Another mail message arrived:

 Subject: Again... Please remove me from this list

but this one was not diverted to the moderators.  What is
wrong with my bounce_matching_headers line?  Thanks.
--
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 240, Room 5.B.8 Internet: bsfin...@anl.gov
Argonne, IL   60439-4828 IBMMAIL:  I1004994
--
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] -owner and -request not working on new host

[Mark Sapiro]

Nina Nicholson wrote:
>
>My problem is that emails sent to both the -owner and -request addresses
>bounce back with the message that that address doesn't exist.
>
>Interestingly I tried to manually created -owner and -request addresses for
>one of the lists (n...@domain.org) via Plesk, and was prevented with the
>message that news-ow...@domain.org and news-requ...@domain.org were already
>in use. So Plesk thinks they exist -- but trying to send anything to them
>fails.


This is apparently a Plesk issue. See the FAQ at
. Debugging this will require access to
the configuration files and logs of the MTA on the Mailman host
machine and perhaps specific Plesk knowledge.

-- 
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] -owner and -request not working on new host

[Nina Nicholson]

I recently moved my site from a host that provided Mailman 2.1.5 and Plesk
8.1 to one that provides Mailman 2.1.9 and Plesk 10.1.1.

I manually created 55 lists on the new host through Plesk, and populated
them in the Mailman admin. All of them have the same two emails in the
-owner field, which were also the same ones used for the old lists on the
old host.

My problem is that emails sent to both the -owner and -request addresses
bounce back with the message that that address doesn't exist.

Interestingly I tried to manually created -owner and -request addresses for
one of the lists (n...@domain.org) via Plesk, and was prevented with the
message that news-ow...@domain.org and news-requ...@domain.org were already
in use. So Plesk thinks they exist -- but trying to send anything to them
fails.

I am not a Linux guru. How do I go about debugging this?
--
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] Approved header, mailman password and security

[Dag Wieers]

Hi,

We have been using the Approved header as a way to automtically approve 
commit logs to a read-only mailinglist. We recently moved our 
infrastructure to github and I wrote a patch to the github Email service 
hook to add an Approved header.


https://github.com/github/github-services/pull/84

Now the problem of course is that this secret currently is either the list 
admin or the list moderator password, which is far from secure. Especially 
if the mails are not created on the mailman list server.


So I would propose to allow to set a separate secret used for approved 
messages. If compromised, it's easy to change that secret on both sides.


Is this acceptable ?

Thanks in advance
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, i...@dagit.net, http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]
--
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] TypeError: cannot concatenate 'str' and 'NoneType' objects

[Jesus Cea]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi. This is a recurrent issue.

This morning I received this:

"""
Your "cron" job on stargate
/usr/local/bin/python2.5 -S /home/mailman/cron/disabled

produced the following output:

Traceback (most recent call last):
  File "/home/mailman/cron/disabled", line 224, in 
main()
  File "/home/mailman/cron/disabled", line 208, in main
mlist.sendNextNotification(member)
  File "/home/mailman/Mailman/Bouncer.py", line 280, in sendNextNotification
msg['Subject'] = 'confirm ' + info.cookie
TypeError: cannot concatenate 'str' and 'NoneType' objects
"""

The problem is, the particular user is marked as "disabled delivery",
but its bounce information is not the responsible for that:

"""
>>> m.getDeliveryStatus("X")
4
>>> m.bounce_info["X"]

"""

So the delivery is disabled because "bounce", but the bounce score is
too low for it (my threshold is 5.0).

When the "cron" executes "disabled" to send out the reminders, it tries
to send to this user, but the process fails because the user is marked
as "bounce" but no confirmation cookie is available.

So, the process dies. No more notifications mails are send. PANIC! :).

I think I can solve this particular case, for a while, doing
"m.setDeliveryStatus("X", 0)". But I will wait a couple of days, just in
case you want me to do any kind of test.

Checking the logs, I see this: (email and listname not shown)

"""
bounce:Apr 13 09:17:59 2011 (1567) list: X bounce score: 1.0
bounce:Apr 13 13:56:29 2011 (5194) list: X already scored a bounce for
date 13-Apr-2011
bounce:Apr 14 09:00:03 2011 (24248) Notifying disabled member X for
list: list
bounce:Apr 14 12:05:16 2011 (12355) Notifying disabled member X for
list: list
bounce:Apr 14 12:06:21 2011 (12546) Notifying disabled member X for
list: list
bounce:Apr 14 12:17:09 2011 (14017) list: X residual bounce received
bounce:Apr 14 13:31:00 2011 (20518) Notifying disabled member X for
list: list
bounce:Apr 14 13:31:15 2011 (20554) Notifying disabled member X for
list: list
"""

So here we have mailman getting a bounce for the address yesterday, and
the original "notification" try and my subsequent tests, today.

Hipotesis: The user set "disable delivery" but we have some bounces
coming back, so the "disable delivery" sets by user is mutated
incorrectly to "user bouncing", causing this problem.

Some more data:

"""
>>> m.getDeliveryStatusChangeTime("X")
1302776230.914567
>>> import time
>>> time.ctime(1302776230.914567)
'Thu Apr 14 12:17:10 2011'
>>> m.getDeliveryStatus("X")
4
"""

The change date, is consistent with this line on my log:

"""
bounce:Apr 14 12:17:09 2011 (14017) list: X residual bounce received
"""

This happens from time to time, and it is really painful, since others
users are not getting their reminders, or they are getting them too late
and their token has already expired.

I will keep this state for a couple of days, just in case you need some
more info. Then, I will clean it up. But this is a recurrent issue,
happens from time to time.

Thanks for your help!

PS: I am using Mailman 2.1.12 with Python 2.5.

- -- 
Jesus Cea Avion _/_/  _/_/_/_/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/_/_/  _/_/_/_/  _/_/
jabber / xmpp:j...@jabber.org _/_/_/_/  _/_/_/_/_/
.  _/_/  _/_/_/_/  _/_/  _/_/
"Things are not so easy"  _/_/  _/_/_/_/  _/_/_/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/_/_/_/  _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBTabjLZlgi5GaxT1NAQJvDwQAk4evdz+3o5rvQ1s0arcPr86vXqdKH4Kp
uqKddRK2GPE8sgjZN704VTUKlDe2BvbftsCTJXIEo2UOvDVy3w95zftYckRVL5f5
Fg0UxPlwG2GjElJLalMKnJyiQ10VGYb6ke+DeXY4EYOYdlzMt0tGvidjjI+obCJv
BuwS0God1O0=
=OCjv
-END PGP SIGNATURE-
--
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] Disallow digest, but getting warning

[Ralf Hildebrandt]

* Ralf Hildebrandt :

> > Warning: You have digest members, but digests are turned off. Those
> > people will not receive mail.
> > 
> > > But WHICH members?
> 
> I patched mailman to emit that info.
> m(

--- /usr/src/mailman-2.1.14/Mailman/Cgi/admin.py2010-12-02 
08:41:27.0 +0100
+++ /usr/src/mailman-2.1.14/Mailman/Cgi/admin.py2011-04-14 
13:34:53.533844622 +0200
@@ -189,11 +189,15 @@
 _('''You have digest members, but digests are turned
 off. Those people will not receive mail.'''),
 tag=_('Warning: '))
+doc.addError(mlist.getDigestMemberKeys(),
+tag=_('Warning: '))
 if not mlist.nondigestable and mlist.getRegularMemberKeys():
 doc.addError(
 _('''You have regular list members but non-digestified mail is
 turned off.  They will receive non-digestified mail until you
 fix this problem.'''), tag=_('Warning: '))
+doc.addError(mlist.getRegularMemberKeys(),
+tag=_('Warning: '))
 # Glom up the results page and print it out
 show_results(mlist, doc, category, subcat, cgidata)
 print doc.Format()


-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de

--
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] Disallow digest, but getting warning

[Ralf Hildebrandt]

* Ralf Hildebrandt :
> * Ralf Hildebrandt :
> > I disallowed my users to get their list-emails (for one list) as a
> > digest.
> > 
> > As far as I can see, I removed the "digest" tickmark for all memeber,
> > yet mailman is reporting:
> > 
> > Achtung: Sie haben Mitglieder, die Nachrichtensammlungen (digests)
> > bekommen wollen, aber der Sammlungs-Modus ist von Ihnen deaktiviert.
> > Diese Mitglieder bekommen deswegen gar keine Nachrichten!
> > 
> > Basically: "Some mebers want digests, you disbaled it, so they're not
> > getting anything".
> 
> Warning: You have digest members, but digests are turned off. Those
> people will not receive mail.
> 
> > But WHICH members?

I patched mailman to emit that info.
m(
--
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] Disallow digest, but getting warning

[Ralf Hildebrandt]

* Ralf Hildebrandt :
> I disallowed my users to get their list-emails (for one list) as a
> digest.
> 
> As far as I can see, I removed the "digest" tickmark for all memeber,
> yet mailman is reporting:
> 
> Achtung: Sie haben Mitglieder, die Nachrichtensammlungen (digests)
> bekommen wollen, aber der Sammlungs-Modus ist von Ihnen deaktiviert.
> Diese Mitglieder bekommen deswegen gar keine Nachrichten!
> 
> Basically: "Some mebers want digests, you disbaled it, so they're not
> getting anything".

Warning: You have digest members, but digests are turned off. Those
people will not receive mail.

> But WHICH members?
--
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] Disallow digest, but getting warning

[Ralf Hildebrandt]

I disallowed my users to get their list-emails (for one list) as a
digest.

As far as I can see, I removed the "digest" tickmark for all memeber,
yet mailman is reporting:

Achtung: Sie haben Mitglieder, die Nachrichtensammlungen (digests)
bekommen wollen, aber der Sammlungs-Modus ist von Ihnen deaktiviert.
Diese Mitglieder bekommen deswegen gar keine Nachrichten!

Basically: "Some mebers want digests, you disbaled it, so they're not
getting anything".

But WHICH members?

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de

--
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