At 4:08 PM +0100 2005-06-14, Andy Heath wrote:
> If the mailman developer community adopts the FHS for
> mailman then that's a different story entirely and
> I would follow without complaint.
SELinux and the FHS are both specific to a particular OS --
Linux. We have to support dozens
>>OFF-TOPIC below:
>>
>>Standards compliance (fedora) is one thing (I work in standards)
>>but when everyone already has a fine standard (put it in the
>>mailman user directory) and the community has no plans
>>to change that then i find it very silly to just throw
>>that away
>
>
> The director
On Tue, 2005-06-14 at 09:50 +0100, Andy Heath wrote:
> If someone could do an ls -R or ls -lR (if there are links)
> of a 2.1.5 mailman directory and post it it would help figure
> out where fedora puts all the pieces (I'll build a list of
> links from it so it looks like a normal mailman director
Mark Sapiro wrote:
> 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 cont
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.
>>
>>
>>
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
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'
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
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
12 matches
Mail list logo
