Mark Sapiro wrote:
>On 07/29/2013 09:55 AM, Barry S. Finkel wrote:
>>
>> Also, as discussed previously on this list, the
>>
>> postfix-to-mailman.py
>>
>> script is NOT part of the SourceForge Mailman, and its use is
>> discouraged. There is a Mailman FAQ that describes this
>> script
On 07/29/2013 09:55 AM, Barry S. Finkel wrote:
>
> Also, as discussed previously on this list, the
>
> postfix-to-mailman.py
>
> script is NOT part of the SourceForge Mailman, and its use is
> discouraged. There is a Mailman FAQ that describes this
> script and the recommendation not to us
On 7/29/2013 11:27 AM, Daniel Pocock wrote:
On 29/07/13 17:53, Mark Sapiro wrote:
On 07/29/2013 08:35 AM, Daniel Pocock wrote:
Migrating to Mailman, I'd like to do something like this:
lists.example.org-list1:
"|/var/lib/mailmen/lists.example.org/mail/mailman post list1"
where I have a ded
On 29/07/13 17:53, Mark Sapiro wrote:
> On 07/29/2013 08:35 AM, Daniel Pocock wrote:
>> Migrating to Mailman, I'd like to do something like this:
>>
>> lists.example.org-list1:
>> "|/var/lib/mailmen/lists.example.org/mail/mailman post list1"
>>
>> where I have a dedicated Mailman install under
On 07/29/2013 08:35 AM, Daniel Pocock wrote:
>
> Migrating to Mailman, I'd like to do something like this:
>
> lists.example.org-list1:
> "|/var/lib/mailmen/lists.example.org/mail/mailman post list1"
>
> where I have a dedicated Mailman install under
> /var/lib/mailmen/lists.example.org just
I currently run virtual domains with Sympa
To get around the aliases file bottleneck and allow pure virtual
hosting, Sympa uses the virtual aliases file to map the recipients like
this:
li...@lists.example.org lists.example.org-list1@myhostname
and each of those entries is then matched
[EMAIL PROTECTED] wrote:
>> 1) Is there any problem with manually adding the extra alias
>> owner-listname for each migrated list and
>> 2) Is is possible that mailman 2.1.9 is generating references to
>> owner-listname and if so, is that a problem?
>
>
>I just found the answer to question 1. I
> 1) Is there any problem with manually adding the extra alias
> owner-listname for each migrated list and
> 2) Is is possible that mailman 2.1.9 is generating references to
> owner-listname and if so, is that a problem?
I just found the answer to question 1. If you add the alias manually it w
Just tried to upgrade by migrating our lists from mailman 1.0 to mailman 2.1.9
on new hardware. Pre-upgrade testing worked fine but after the real migration
I saw a lot of "user unknown" errors in postfix's maillog.After
investigating I found a lot of rejected mail destined for owner-listna
On 4/22/05, Dan Phillips <[EMAIL PROTECTED]> wrote:
>
> On Apr 22, 2005, at 11:39 AM, Dave Pisarek wrote:
> > RuntimeError: command failed: /usr/sbin/postalias
> > /usr/local/mailman/data/aliases (status: 1, Operation not permitted)
> >
> > When I check the aliases file it is owned by root in the
Each time I attempt to create a list in Mailman version 2.1.5 I
receive the following:
RuntimeError: command failed: /usr/sbin/postalias
/usr/local/mailman/data/aliases (status: 1, Operation not permitted)
When I check the aliases file it is owned by root in the group mailman,
-rw-rw 1 root
if MTA sendmail after i create list, i add some script in aliases file. if i using
SMTP server in Domino Server where i put that script
can some body help me!!
-
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
-
I just installed Mailman 2.1.1, python 2.2.2, Redhat 7.1, sendmail
8.11.6. Mailman works great if I do not use a catchall email address
in my /etc/mail/virtusertable . If I activate the catchall address,
the addresses in the aliases file do not work. Is there a work around
for this issue. I use
13 matches
Mail list logo
