Thanks Mark. Just the advise that was needed.
Turns out that my script in init.d/ couldn't find its pid and so didn't
known how to shut anything down. I had to use kill pid commands from
the ps listing. But when it restarted, the archive runner started up
with the rest of them and the archive
Teck wrote:
>
>config suse 10.0 postfix spanassassin amavisd clamd freshclam all running
>mailman DID work. im not sure just yet when it quit. anyone of the members
>can send to it and mailman does its thing and mail gets delivered to any
>members of MY domain. it will not send to outside d
> On Apr 29, 2007, at 2:27 PM, Teck wrote:
>
>> i have been trying to figure this out for the last day and a half google
>> is
>> not my friend !:(
>>
>> config suse 10.0 postfix spanassassin amavisd clamd freshclam all
>> running
>> mailman DID work. im not sure just yet when it quit. anyo
[EMAIL PROTECTED] wrote:
>
>The comment "... and was distributed to all members" turns out to be
>incorrect. Messages from 'new' subscribers are delivered by MailMan
>to *some* existing members of the mailing list, but definitely not all
>of them.
>
>The bottom line is that for the moment, our att
Hugh Esco wrote:
>
>The moderation que appropriately snags unauthorized mail. The list is
>passing traffic through to the list. But so far, I have seen no
>evidence that anything is being archived, although I believe I've
>appropriately configured these new lists to do that.
>
>The root adminis
On Apr 29, 2007, at 2:27 PM, Teck wrote:
> i have been trying to figure this out for the last day and a half
> google is
> not my friend !:(
>
> config suse 10.0 postfix spanassassin amavisd clamd freshclam
> all running
> mailman DID work. im not sure just yet when it quit. anyone of
>
A correction to the 'analysis' below:
--> --> >A message from a newly added subscriber is accepted, logged in the
--> --> >archive, and distributed to all the members of the mailing list.
-->
--> I just reconfirmed this, by adding myself again with yet another new
--> address, then sending a mess
I've been using multiple instances of mailman for probably close to a
hundred different lists on dozens of projects since 2000. I've
administered dozens of mailman installations on at least six servers,
many of them with command line access. I have never run into this issue
before.
I have set
i have been trying to figure this out for the last day and a half google is
not my friend !:(
config suse 10.0 postfix spanassassin amavisd clamd freshclam all running
mailman DID work. im not sure just yet when it quit. anyone of the members
can send to it and mailman does its thing and m
