After following all your directions, I have a working mailman system, THANK
YOU!!
Best regards,
Ron
signature.asc
Description: This is a digitally signed message part.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.o
On 2/5/2011 8:51 AM, Ron Aaron wrote:
>
> Here goes. I'm not sure if I mentioned that this is an "ispconfig3" based
> setup, don't know if that makes a difference (but it may). Output of
> postconf
> -n follows:
>
> alias_maps = hash:/var/lib/mailman/data/aliases
Remove the above. It is for
> It may have something to do with passing through spamassassin, but I
> don't think so because queue id 5C9BB541603 is the message after
> spamassassin and it notes orig_to=. However, I'm not
> sure why the message is handled by Postfix's pipe module. That seems odd.
Right. I've also noticed th
On 2/3/2011 10:54 PM, Ron Aaron wrote:
>
> After re-setting things as you mentioned above, and restarting the daemons, I
> sent an email to my test list. Here is the relevant mail.log:
>
> postfix/smtpd[16482]: connect from unknown[192.168.18.100]
> postfix/smtpd[16482]: setting up TLS connecti
You wrote:
> Which indicates Postfix is not seeing that mail to lists.my.dom is
> using the mailman transport.
Right.
> Have you added hash:/etc/mailman/transport to transport_maps in
> main.cf? have you run "postmap /etc/mailman/transport" to update
> /etc/mailman/transport.db?
Yes I have, and
Ron Aaron wrote:
>
>I created a new domain "lists.my.dom", where the "my.dom" is the actual doman.
>
>In postfix "main.cf" I added a special "/etc/mailman/transport" which has the
>single line:
>
>
> lists.my.dom mailman:
>
>
>The default setup of master.cf already has an appropriate mail
I've got an "ispconfig3" based Ubuntu 10.10 server installation, running
postfix. The mail server works perfectly.
I wish to add mailman to the setup, and am hitting a brick wall. I've looked
all over for clues, but no luck so far.
I created a new domain "lists.my.dom", where the "my.dom" i
