>>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 the looping, but you want at least > > subject:.*\[spam\].*
silly me, I should (and do) know that. But still it shouldn't loop as you say (its a legal RE without the escaping). > > as the regexp. > > What are the reasons (error log, smtp-failure log ?) for the failure in > the notification 'loop'? 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 data directory fills up with .pck files and directories in the spool dir fill up with mail files. I was testing with only one member, one administrator and one or two mails so the looping was obvious. Some boundary condition is failing in the code. I decided I would inform the other admins about this flakeyness and work around it but would it be useful if I set up the situation again and posted the log file contents ? Having been happy with mailman for years this one surprised me (you come to depend on its reliability). The other problem concerns me more because I can't find a good way around it that triggers action from moderators. bogey > > -- > Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp