On Thu, Aug 25, 2011 at 12:20 PM, Marcos Luis Ortiz Valmaseda <
marcosluis2...@googlemail.com> wrote:
> Well, test it and say the response to us.
>
So the first issue was:
SELinux is preventing /usr/sbin/postalias from search access on the
directory /etc/postfix.
It then complained (one at a tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/25/2011 11:52 AM, Fulko Hew wrote:
> On Fedora 14, I am setting up postfix and mailman.
>
> I had this working once, but I decided to yum erase postfix and
> mailman and redo the configuration to prove I knew how to recreate
> it.
>
> Turns out
Well, test it and say the response to us.
2011/8/25 Fulko Hew
>
>
> On Thu, Aug 25, 2011 at 12:13 PM, Marcos Luis Ortiz Valmaseda <
> marcosluis2...@googlemail.com> wrote:
>
>> Can you provide the ls -Z of your content in /etc/mailman/aliases
>>
>
> [root@netwatch log]# ls -Z /etc/mailman/alia
On Thu, Aug 25, 2011 at 12:13 PM, Marcos Luis Ortiz Valmaseda <
marcosluis2...@googlemail.com> wrote:
> Can you provide the ls -Z of your content in /etc/mailman/aliases
>
[root@netwatch log]# ls -Z /etc/mailman/aliases
-rw-rw. root mailman unconfined_u:object_r:mailman_data_t:s0
/etc/mailma
Can you provide the ls -Z of your content in /etc/mailman/aliases
A advice:, use sealert to see a more human-readable approach to analyze the
SELinux logs.
2011/8/25 Fulko Hew
> On Fedora 14, I am setting up postfix and mailman.
>
> I had this working once, but I decided to yum erase postfix an
On Fedora 14, I am setting up postfix and mailman.
I had this working once, but I decided to yum erase postfix and mailman
and redo the configuration to prove I knew how to recreate it.
Turns out I don't know how to recreate a working combination
because when creating a new list I now have mailma