[Mailman-Developers] Advice wanted on option to not include original post in notices

2006-03-27 Thread Mark Sapiro
Last week, I posted the following to the mailman-users list. The silence 
was deafening as they say (I actually got one good response, but only 
one). So, does anyone here want to offer an opinion?

There have been a couple of threads on the (mailman-users) list in the 
last week or two regarding not sending the content of the original post 
in reject notices to the (alleged) poster and in owner notifications.

I'm considering implementing these options for Mailman 2.2, but I want
some feed back to be sure I'm doing what people want and to be sure
I'm not overlooking things.

Here are my areas of concern.

First, should these be site wide mm_cfg.py options or should they be
per-list options with a default from mm_cfg.py? In either case, the
Defaults.py setting would match current behavior.

I see a few different cases of notices which include the original message.

Bounce processing sends unrecognized bounces to the owner if
bounce_unrecognized_goes_to_list_owner is on. Since these notices are
meaningless without the actual message, I think there is no need for
an additional setting here. Also, if bounce_notify_owner_on_disable is
on, the owner gets a copy of the triggering bounce, but this should
always be a legitimate DSN in response to a message from the list, so
I don't see a need to provide an option to exclude the DSN from the
notification.

The privacy options reject_these_nonmembers, generic_nonmember_action
and header_filter_rules can automatically reject a post. Currently,
the original post is included. I foresee a single option (should it be
site wide or per list) to control putting the original in the reject
notice.

The moderator can reject a held post. Currently the original post is
not included. I don't see a need to change this.

If admin_immed_notify is on, notices of individual held posts are sent
to the owners/moderators and these include the original post. I foresee 
an option separate from the reject option (and should this be site wide
or per list) to put only summary information (From:, Subject: hold
reason) in this notice.

Note that this last can be 'almost' accomplished currently by turning
admin_immed_notify off and increasing the frequency of the
cron/checkdbs job from daily to maybe hourly, although this would
affect all lists.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

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


Re: [Mailman-Developers] Advice wanted on option to not include original post in notices

2006-03-27 Thread Giuliano Gavazzi

On 28 Mar 2006, at 01:48, Mark Sapiro wrote:

> The privacy options reject_these_nonmembers, generic_nonmember_action
> and header_filter_rules can automatically reject a post. Currently,
> the original post is included. I foresee a single option (should it be
> site wide or per list) to control putting the original in the reject
> notice.

per list seems better. I personally don't like mailman being allowed  
at all to bounce to the alleged sender, but this is another matter..

Giuliano


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

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


Re: [Mailman-Developers] Advice wanted on option to not include original post in notices

2006-03-27 Thread John W. Baxter
On 3/27/06 3:48 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote:

> First, should these be site wide mm_cfg.py options or should they be
> per-list options with a default from mm_cfg.py? In either case, the
> Defaults.py setting would match current behavior.

> [Other good thoughts deleted, as Mark knows what he said]

Hi, Mark

It is the site's reputation which (increasingly with more aggressive
anti-spam in the world) suffers from bounces containing the content.  So
messages heading out of the site to the world should be controlled by the
site as to whether the content is included.

It should be up to the list administrator what (non-bounce) message bodies
reach the administrator/moderator in email.  (Personally, I don't much care
as long as the whole thing remains visible in the web interface.  I get
ideas about servers to block.)

I agree that bounces without content are pretty useless...so they should go
to list administrators.

Sorry I didn't answer last week...I was busy.

  --John


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

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