headers
Jeffrey Borkent | 1 Feb 2005 01:24
Picon
Picon
Favicon

ldap queries......

Hi,

Here at the University of Adelaide we have several very large lists that
are generated by ldap queries. A module offered to us by Karl A. Krueger
at the Woods hole Oceanographic Institute works a treat, and generates
the lists based on ldap search criteria.

What we wish to do now is restrict who can send to the list without
moderator intervention. Take for example the all student list here,
currently we have another ldap entry which authorises posting to this
list. 

My question is where in the current Mailman code ( v2.1.5 ) can we place
some code to check this ldap authorisation entry?

Cheers

--

-- 
Jeffrey Borkent
Systems Specialist
Information Technology Services
University of AdelaideKarl A. Krueger
Level 7, 10 Pultney Street
Adelaide. 5005
Ph: 8303 3000
jeffrey.borkent <at> adelaide.edu.au

---------------------------------
CRICOS Provider Number 00123M
-----------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ivan Fetch | 1 Feb 2005 02:28
Picon
Favicon

respond_to_post_requests and header_filter_rules

Hello,

    I'm wondering whether there is a way to have respond_to_post_requests 
set to yes (so that senders will be notified if their message is held due 
to posting to a members-only list, their message exceeds mailman's size 
limit, Etc), yet not send notifications to senders who's messages are 
held because they match a filter 
rule (privacy | spam ).

    The help section of respond_to_post_requests says the following, which leads me to believe that it will
not notify senders 
of messages which match spam filter rules:
"Approval notices are sent when mail triggers certain of the limits except 
routine list moderation and spam filters, for which notices are not sent. 
This option overrides ever sending the notice."

    However when I send a message to a list and it matches against a spam 
filter, I receive an email back notifying me that my message was held 
because a filter was matched.  It would be nice to be able to avoid 
responding to messages which Mailman matches against the spam filters, as 
often the From address is forged anyhow...

    IS there something I'm missing which will give me the behavior I'm 
looking for RE: spam filtering?

Thank you - Ivan Fetch.
Permalink | Reply | 0 comments |
headers
Mark Sapiro | 1 Feb 2005 02:50

Re: ldap queries......

Jeffrey Borkent wrote:
>
>Here at the University of Adelaide we have several very large lists that
>are generated by ldap queries. A module offered to us by Karl A. Krueger
>at the Woods hole Oceanographic Institute works a treat, and generates
>the lists based on ldap search criteria.

Presumably, this is a Member Adaptor module

>What we wish to do now is restrict who can send to the list without
>moderator intervention. Take for example the all student list here,
>currently we have another ldap entry which authorises posting to this
>list. 
>
>My question is where in the current Mailman code ( v2.1.5 ) can we place
>some code to check this ldap authorisation entry?

Whatever Member Adaptor is in use for a list defines a function
getMemberOptions(self, member, flag) in that module. In your case,
this should be in the module referred to above. You need to arrange
that whenever this is called with flag = mm_cfg.Moderate, it returns
True (or 1) if member should be moderated and False (or 0) if member
should not be moderated.

I.e. you need to place your code in getMemberOptions() in your Member
Adaptor.

Note: your Member Adaptor module may be called extend.py and be
installed in a lists/<listname>/extend.py file for each list for which
it applies or it may have some other name and be invoked globally in
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tokio Kikuchi | 1 Feb 2005 03:39
Picon
Favicon

Re: respond_to_post_requests and header_filter_rules

Hi,

Ivan Fetch wrote:

> Hello,
> 
>    I'm wondering whether there is a way to have respond_to_post_requests 
> set to yes (so that senders will be notified if their message is held 
> due to posting to a members-only list, their message exceeds mailman's 
> size limit, Etc), yet not send notifications to senders who's messages 
> are held because they match a filter rule (privacy | spam ).
> 
>    The help section of respond_to_post_requests says the following, 
> which leads me to believe that it will not notify senders of messages 
> which match spam filter rules:
> "Approval notices are sent when mail triggers certain of the limits 
> except routine list moderation and spam filters, for which notices are 
> not sent. This option overrides ever sending the notice."
> 

Looks like this detail is outdated. I think new spam filters should be 
used to silently discard the known spams. Ivan, what version are you 
using? Newer version has more generic header_filter_rules to 
hold/reject/discard such messages.

Developers, I think I will remove 'spam filters' from the detailed 
description above but what is the 'routine list moderation'? I think 
list-wide moderation was replaced by per-member moderation, right?
> 
>    However when I send a message to a list and it matches against a spam
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dikshie | 1 Feb 2005 05:11
Picon
Favicon

Re: always forbidden

Brad Knowles (brad <at> stop.mail-abuse.org) wrote:
> 
> 	There's your answer.  It's a web server configuration issue.

thanks !
Kikuchi-san's tip works for me

best regards,

-dikshie-
Permalink | Reply | 0 comments |
headers
Ivan Fetch | 1 Feb 2005 05:59
Picon
Favicon

Re: respond_to_post_requests and header_filter_rules

Hello,

    Thank you for your reply -- I'm using Mailman 2.1.5 (sorry for not 
mentioning this previously).  We'd rather be able to configure the filters 
to hold (not discard) spam, at least for those lists where the list 
administrators prefer to double check what is being tagged as spam.

    Is the help text of respond_to_post_requests inaccurate in how it 
claims that notifying posters of held messages excludes spam filtering?

Thank you - Ivan Fetch.

---
Ivan Fetch
University of Denver
Computer Operations, University Technology Services
303-871-3092

On Tue, 1 Feb 2005, Tokio Kikuchi wrote:

> Hi,
>
> Ivan Fetch wrote:
>
>> Hello,
>> 
>>    I'm wondering whether there is a way to have respond_to_post_requests 
>> set to yes (so that senders will be notified if their message is held due 
>> to posting to a members-only list, their message exceeds mailman's size 
>> limit, Etc), yet not send notifications to senders who's messages are held
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bashir Ghandi | 1 Feb 2005 08:43
Picon
Favicon

How do I Customize the Monthly Reminder?

Hi there,

I am a Mailman mailing list owner, and I am trying to
cutomize the monthly reminder or at least append some
custom text to it, but could not figure out how.

I checked all the options on the List admin interface
but no clue.

Please note that I do have direct access to the
machine hosting the mailman, as I am only a mailing
list owner - so I have only the List Administrator's
Web Interface to work with.

Thanks a million in advance for your help.

Bashir.

	
	
		
___________________________________________________________ 
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
Permalink | Reply | 0 comments |
headers
Matthew R Anderson | 1 Feb 2005 09:33

Mailman problem

Hey guys-

I don't mean to give you such a tough problem but I really need some expert
help here.  I've moved my mailman install across a few servers and as of
recent it's been exhibiting some strange behavior.

Key Problem - Monthly reminders aren't being sent out to some lists; I have
several configured to do so.  I've checked logs/smtp, logs/smtp-failure, and
logs/error and I can't even see an attempt to mail reminders, let alone any
errors to provide an explanation.  In all other regards, lists seem to be
working wonderfully, and I've really not begun to tackle this problem after
2 months because I've been so blessed.

The one thing I can see that seems to coincide with the trouble is that any
action on these lists isn't being properly logged in logs/smtp.  Whereas I
would properly see something logged like so:

Jan 31 00:47:35 2005 (1192) <mailman.0.1107154053.16170.list <at> lists.iddx.net>
smtp for 538 recips, completed in 1.197 seconds

...when I see activity on the "questionable" lists, I see this:

Feb 01 02:01:36 2005 (1192) n/a smtp for 22 recips, completed in 2.479
seconds

n/a?  :)  I can't seem to locate any explanation for this.  Help!

Furthermore, is there a way to manually generate password reminders?  I'd
like to be able to manually kick out a reminder once I get this all fixed
up.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Markus Darges | 1 Feb 2005 10:17
Picon

Re: cant't create lists within the webinterface

John Dennis wrote:

>On Mon, 2005-01-31 at 11:01 +0100, Markus Darges wrote:
>  
>
>>Hi,
>>
>>I cant' create a new list within the webinterface. Could someone tell 
>>mit whether it's a known bug? Even if  I change the permission of the 
>>folder lists to 777 I get the same error.
>>My OS is Fedora Core 3. Mailman 2.1.5, Python2.4, Apache2.0.52
>>    
>>
>
>First, off I trust you are using Red Hat's mailman rpm for FC3.
>
>There is a possibility you may have run afoul of SELinux, but its very
>hard to tell from the information presented. SELinux is a security
>enhancement that restricts operations beyond the traditional UNIX
>permissions. In FC3 SELinux is enabled by default in what is called
>"targeted" mode, meaning SELinux is only used for "targeted"
>applications and services because those applications and services are
>open to the network and are much more vulnerable to exploit, mailman is
>one of the services under SELinux protection. The security policy is
>non-trival to author correctly it is possible we may have missed a
>corner case. Here are two simple things you can do to determine if
>SELinux is responsible for your access problems.
>
>1) Look in /var/log/messages for any lines with "avc" in it, it will
>probably read something like "audit avc access denied ..." but I'm going
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tokio Kikuchi | 1 Feb 2005 12:39
Picon
Favicon

Re: respond_to_post_requests and header_filter_rules

Hi again,

Ivan Fetch wrote:

> Hello,
> 
>    Thank you for your reply -- I'm using Mailman 2.1.5 (sorry for not 
> mentioning this previously).  We'd rather be able to configure the 
> filters to hold (not discard) spam, at least for those lists where the 
> list administrators prefer to double check what is being tagged as spam.
> 

You can create two or more new header_filter_rules. I suggest you create 
one for hold and another for discard. You can add a test regex into the 
first box and when you learn that it works right then move it to the 
second one to discard the spam silently.

>    Is the help text of respond_to_post_requests inaccurate in how it 
> claims that notifying posters of held messages excludes spam filtering?

Historically, it was right statement once upon a time in 2.0.x era.

--

-- 
Tokio Kikuchi, tkikuchi <at>  is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Permalink | Reply | 0 comments |

Gmane