On 08/08/2015 06:22 PM, Steve Matzura wrote:
> On Sat, 08 Aug 2015 12:39:19 -0700, Mark asked:
>
>> What does
>>
>> groups mailman
>>
>> report? It should be 'mailman : mailman'. If so, and the crons are
>> getting permission problems, check if SELinux is enabled and if so, try
>> disabling it.
>
On Sat, 08 Aug 2015 12:39:19 -0700, Mark asked:
>What does
>
>groups mailman
>
>report? It should be 'mailman : mailman'. If so, and the crons are
>getting permission problems, check if SELinux is enabled and if so, try
>disabling it.
It's "mailman : mailman postfix", and SELinux is disabled acco
On Sat, 08 Aug 2015 09:19:27 -0700, Mark Sapiro
wrote:
>On 08/08/2015 08:12 AM, Steve Matzura wrote:
>> Every night, I get the following error at the bottom of a mail message
>> to my mailman list telling me that checkdbs, digest and disabled
>> failed:
>>
>> IOError: [Errno 13] Permission denie
On 08/08/2015 10:26 AM, Larry Turnbull wrote:
>
> I just checked the system and I see /var/spool/crontab/mailman.
OK, this is the user crontab for the user 'mailman'.
> /etc/cron.d/mailman does not exist so it is running under the first
> scenario.
Normally /etc/cron.d/mailman does not exist
I am working with Steve on this one as well.
I just checked the system and I see /var/spool/crontab/mailman.
/etc/cron.d/mailman does not exist so it is running under the first
scenario.
If I type crontab -u mailman -l I can see the list of mailman cron jobs that
are scheduled to run.
I am tryi
On Sat, Aug 8, 2015 at 11:43 AM, Jim Popovitch wrote:
> On Wed, Aug 5, 2015 at 3:15 AM, Jayson Smith
> wrote:
>>
>> A few months ago I did some Googling and found a project called
>> Mailman-Milter which claims to reject unwanted list mail i.e., nonmember
>> postings at the SMTP level. I would l
On 08/08/2015 08:12 AM, Steve Matzura wrote:
> Every night, I get the following error at the bottom of a mail message
> to my mailman list telling me that checkdbs, digest and disabled
> failed:
>
> IOError: [Errno 13] Permission denied:
> '/usr/local/mailman/locks/mailman.lock.{my-FQDN}.{some-num
On Wed, Aug 5, 2015 at 3:15 AM, Jayson Smith wrote:
>
> A few months ago I did some Googling and found a project called
> Mailman-Milter which claims to reject unwanted list mail i.e., nonmember
> postings at the SMTP level. I would love to use this, but there's virtually
> no documentation and I'
Every night, I get the following error at the bottom of a mail message
to my mailman list telling me that checkdbs, digest and disabled
failed:
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/locks/mailman.lock.{my-FQDN}.{some-number}.0'
This also happened on the one and only password
Nick Stevens via Mailman-Users wrote:
>I think a good starting point would be to get back to defaults on everything.
The method I used was similar to Mark's, but I exported the settings from both
the new and the current list to a text file and ran diff on those files to see
exactly what people
Jayson Smith wrote:
>I've been running several Mailman lists for the past ten years or so.
>Unfortunately, in recent months some list addresses have fallen into the hands
>of spammers, which is a real headache. Even worse, one particular -owner
>address is receiving nothing but spam, and I don'
11 matches
Mail list logo
