On Jun 9, 2005, at 01:52, Mark Sapiro wrote:
> I think I see the problem with the listinclusion patch. It locks the
> @list list and doesn't unlock it. I don't see a need to lock the list,
Thanks Mark! I've made that change as well as finally patching the
help for accept_these_nonmembers. The
At 1:17 PM -0500 2005-06-13, Tracey McCartney wrote:
> Is this "external membership sources" feature documented somewhere yet, and
> can it be implemented by list administrators, or is it available only to
> the folks who have access to the server Mailman's running on?
There's the LDAP
Tracey McCartney wrote:
>The Mailman home page thanks control.com for their sponsorship of, among
>other things, "external membership sources" in the new version of Mailman.
>
>Is this "external membership sources" feature documented somewhere yet, and
>can it be implemented by list administrato
SAA wrote:
>
>admin links giving localhost.localdomain so links not working. everything
>else works except for this. Normal emails to lists and list owners are fine
>but when it goes to the mailman owner of the whole server it shows this link
>in the bottom. Here is a example
>
>As list administrat
Andy Heath wrote:
>
>so how does "subject:.*[SPAM}.*" (admitredly meaning s or p etc) trigger
>the behaviour but "subject.*spam" not trigger it ?
Because on the second and subsequent passes through it is looking at
the subject of the notice to the owner which contains 's', 'p', 'a'
and 'm' but no
Andy Heath wrote:
>Mark Sapiro wrote:
>
>> Andy Heath wrote:
>>
>>>they don't show as fails at all. What appears to happen is
>>>mailman keeps trying to send the mail and succeeding
>>>but it keeps doing it again and again. Meanwhile no
>>>mail leaves, it just sits in the spool dir.
>>
>>
>>
The Mailman home page thanks control.com for their sponsorship of, among
other things, "external membership sources" in the new version of Mailman.
Is this "external membership sources" feature documented somewhere yet, and
can it be implemented by list administrators, or is it available only to
Mark,
>> Since this subject matches .*[spam].*, the message to the owner is
>> identified as spam and the whole thing goes again.
> Not sure I understand you. It doesn't get as far as the usual
> sendmail queues. How does the subject get parsed twice ?
>
> The solution is to not use regexps
admin links giving localhost.localdomain so links not working. everything
else works except for this. Normal emails to lists and list owners are fine
but when it goes to the mailman owner of the whole server it shows this link
in the bottom. Here is a example
As list administrator, your auth
Mark Sapiro wrote:
> Andy Heath wrote:
>
>>they don't show as fails at all. What appears to happen is
>>mailman keeps trying to send the mail and succeeding
>>but it keeps doing it again and again. Meanwhile no
>>mail leaves, it just sits in the spool dir.
>
>
> What spool directory? The MTA'
On 6/8/05, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Ryan Rempel wrote:
>
>> I am having a problem with messages sometimes being silently dropped
>> after being approved.
>
> I don't know if this is happening in your case, but one way this can
> happen is if content filtering discards the message
Andy Heath wrote:
>
>they don't show as fails at all. What appears to happen is
>mailman keeps trying to send the mail and succeeding
>but it keeps doing it again and again. Meanwhile no
>mail leaves, it just sits in the spool dir.
What spool directory? The MTA's?
>The data directory fills up
>>subject:.*[SPAM].*
>
>
> The upper/lower case is immaterial as thes matches ale all
> 'ignorecase', but you don't want the above regexp in any case since
> [SPAM] is a character set so the regexp matches anything with an 's',
> 'p', 'a' or 'm' in the subject.
>
> I don't know what would cause
Andy Heath wrote:
>
>1. regex matching with some regex'es
>causes mailman to loop trying to send
>mail to the list-owner and failing.
>
>e.g.
>this seems ok
>
>subject:.*spam
>
>but this one causes looping
>
>subject:.*[SPAM].*
The upper/lower case is immaterial as thes matches ale all
'ignorecase
>See the whole thread that starts at
>http://mail.python.org/pipermail/mailman-users/2005-January/041742.html
Good info, thanks.
In addition: might there be means to contribute money to this
effort? (I'm thinking around $100 for now.)
I'm also interested to know how popular such a virtual-do
Matt England wrote:
>
>Alternatively, has anyone been asking the Cpanel people about what changes
>they made to Mailman to support full Virtual Domains (ie, email lists with
>same name on 2 diff domains via the same Mailman install binary)? Could
>these sorts of changes possibly make it into a
Matt England wrote:
>
>I think I get the high-level concept here, but I'm fuzzy on some things,
>including how to implement this.
>
>Is this how one can/should it? In this context:
>
> Default URL and email host domain = lists.default.tld
> Virtual URL and email host domain = list
At 6/12/2005 11:10 PM, Mark Sapiro wrote:
>[...] it [full Virtual Domain support] probably won't happen before Mailman 3.
I know open-source projects usually do no react well to this question, but
I'll try anyway:
Is there a rough timeline for Mailman 3? eg, which "order of magnitude"
shall
At 6/13/2005 12:19 AM, Mark Sapiro wrote:
>Matt England wrote:
> >
> >Can anyone provide recommendations for configuring the 'mailman' email
> >list...that spans the virtual domains? Should one alias the virtual domain
> >'mailman' list somehow to the "global" mailman list?
>
>I assume here you're
From
http://sourceforge.net/tracker/index.php?func=detail&aid=1219686&group_id=103&atid=100103
:
I find that if I want to support qmail-to-mailman.py for
multiple virtual domains I must add a:
local = re.sub("^lists.newdomain.tld-","",local)
line for every virtual domain.
Could qmail-to-ma
Using 2.1.5 on fedora cors 3. Run an old
mailman for years but just setting this
one up afresh.
Two probs - some regexes and preventing
spams going to moderators while holding
them back:
1. regex matching with some regex'es
causes mailman to loop trying to send
mail to the list-owner and failing
21 matches
Mail list logo
