Helmut Schneider wrote:
>From: "Mark Sapiro"
>> Helmut Schneider wrote:
>>>
>>> I did not touch the MTA setting, the only things I added are
>>>
>>> DEFAULT_EMAIL_HOST
>>> DEFAULT_URL_HOST
>>> DEFAULT_URL_PATTERN
>>> PUBLIC_ARCHIVE_URL
>>> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>>>
From: "Mark Sapiro"
Helmut Schneider wrote:
I did not touch the MTA setting, the only things I added are
DEFAULT_EMAIL_HOST
DEFAULT_URL_HOST
DEFAULT_URL_PATTERN
PUBLIC_ARCHIVE_URL
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DELIVERY_MODULE = 'SMTPDirect'
SMTPHOST
SMTPPORT
Communica
Whit Blauvelt wrote:
>Okay, after an old Gentoo server died that was running mailman happily for
>years with sendmail, I rebuilt things on Ubuntu using a stock postfix with a
>custom-compiled mailman. The web interface all looks fine - the lists and
>their users are there - and the aliases are in
Salvatore D'Agostino wrote:
>Does anyone know where I can set the default settings for all newly
>created lists so that I won't have to always log in to the website each
>time and set them individually?
Most list settings have defaults in Mailman/Defaults.py. Read that file
to see what the set
Daniel Novotny wrote:
>
>we are now having a problem, how to adapt mailman configuration (mm_cfg.py)
>to SELinux policy:
>
>it resides in /usr and the SELinux maintainer argues /usr should be read-only,
>which is not satisfied, when you change the configuration (and the .pyc file
>has to be generat
Helmut Schneider wrote:
>
>I did not touch the MTA setting, the only things I added are
>
>DEFAULT_EMAIL_HOST
>DEFAULT_URL_HOST
>DEFAULT_URL_PATTERN
>PUBLIC_ARCHIVE_URL
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>DELIVERY_MODULE = 'SMTPDirect'
>SMTPHOST
>SMTPPORT
>
>Communication itself
Salvatore D'Agostino wrote:
>Does anyone know where I can set the default settings for all newly
>created lists so that I won't have to always log in to the website each
>time and set them individually?
>
>Thanks in advance =)
I have 25 list template files that I use when I create a list via
t
hello,
we are now having a problem, how to adapt mailman configuration (mm_cfg.py)
to SELinux policy:
it resides in /usr and the SELinux maintainer argues /usr should be read-only,
which is not satisfied, when you change the configuration (and the .pyc file
has to be generated in /usr/lib/mailman
Hi Mark,
From: "Mark Sapiro"
Mark Sapiro wrote:
Helmut Schneider wrote:
I set up a new mailman instance (2.1.11). I remeber that when I
created new lists a mail was sent to the admin describing what he
needs to add to /etc/aliases to make the new list work. Currently I
do not recieve that