Hi Mark.
It appears your ISP is using some packaged Mailman (possibly Debian or
RedHat), but has not properly configured Postfix to look for Mailman's
aliases and virtual maps in the place where the package puts them.
It's a VM with CentOS and I guess he simply picked the package from Yum.
I
Ulf Dunkel wrote:
>
>When I run /usr/lib/mailman/bin/genaliases, I see that in /etc/mailman/
>the relevant files are updated:
>
>- aliases
>- aliases.db
>- virtual-mailman
>- virtual-mailman.db
>
>But Postfix won't react on alias changes until I copy at least the
>aliases* files into /var/lib/mai
Andreas Achtzehn wrote:
>
>I have copied the complete mailman tree to the NFS share. The
>configuration works fine, mails are delivered and I can work within in
>the web interface on the other server.
>Unfortunately, removing lists doesn't work, because NFS doesn't support
>locking.
Since it is
Thank you for all your ideas. I was just a bit surprised that a list
would be available for anyone to post to, since we emphasize to our
users that their lists are protected from spam, as all lists require
you to be a subscribe to post, and many require mod permissions to
post. That is still true a
Christopher Adams wrote:
>Thanks, Mark. That seemed too obvious. Doesn't setting
>generic_nonmember_action to accept result in a lot of spam to the
>Mailman site admin? How are others dealing with this?
First, let me say that if your listinfo overview page says "If you are
having trouble using t
-- Christopher Adams <[EMAIL PROTECTED]> is rumored to have mumbled on 23.
Mai 2007 11:39:48 -0700 regarding Re: [Mailman-Users] mailman aliases:
Thanks, Mark. That seemed too obvious. Doesn't setting
generic_nonmember_action to accept result in a lot of spam to the
Mailman site adm
Thanks, Mark. That seemed too obvious. Doesn't setting
generic_nonmember_action to accept result in a lot of spam to the
Mailman site admin? How are others dealing with this?
On 5/22/07, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Christopher Adams wrote:
>
> >Thanks,Mark. That helps explaining the p
Christopher Adams wrote:
>Thanks,Mark. That helps explaining the purpose of the mailman list.
>
>All our lists use the form [EMAIL PROTECTED] (wherever.com is the
>DEFAULT_EMAIL_HOST set in mm_cfg.py).
>
>In my Postfix aliases file, I have all the list aliases including
>aliases for the mailman li
Thanks,Mark. That helps explaining the purpose of the mailman list.
All our lists use the form [EMAIL PROTECTED] (wherever.com is the
DEFAULT_EMAIL_HOST set in mm_cfg.py).
In my Postfix aliases file, I have all the list aliases including
aliases for the mailman list:
## mailman mailing list
mail
Christopher Adams wrote:
>Just for clarification, what is the use for the mailman list that is
>listed in the aliases file? Is this a required list and if so, what is
>it's purpose.
It is a required list in Mailman 2.1. bin/mailmanctl will not start
Mailman if it isn't present. It is used as the
>>> <[EMAIL PROTECTED]> 5/3/02 11:09:44 AM >>>
Someone was kind enough (in the RH mailing list) to mention something about
setting up aliases and then rebuilding the Alias table for postfix.
How do I do that?
When you create a new list, Mailman tells you the aliases that need to be created;
[EMAIL PROTECTED] wrote:
>
> Howdy!
>
> Been working since yesterday to get a PostFix/QPopper/Mailman configuration
> installed and think that I'm JUST about there. Problem is when I send a message
> to [EMAIL PROTECTED] or [EMAIL PROTECTED] or any other
> address related to the list, my email s
12 matches
Mail list logo
