mailman integration problems

[BilldaCat]

I thought I had this integrated right, but when I try to send an e-mail to the list (list@mydomain.org), Zimbra acts as if it's a bad address. I can send e-mails to existing accounts (me@mydomain.org) fine.

The problem I think is in the postfix config .. the directions say to change these lines:

virtual_alias_maps = ldap:/opt/zimbra/conf/ldap-vam.cf,hash:/usr/local/mailman/data/virtual-mailman
alias_maps = hash:/etc/aliases,hash:/usr/local/mailman/data/aliases

I changed the first one with zmlocalconfig, the second I couldn't find in there, so I changed it in main.cf.default, but when restarting zimbra it doesn't seem to make it's way into main.cf. That's one issue and could end up resolving the whole thing.

Another odd problem is when I have that virtual_alias_maps line modified and try to send any email, local or not, Zimbra hangs and eventually returns a error.

Any ideas?

[BilldaCat]

got both of them in main.cf, but still same problem. zimbra times out trying to send the mail.

[phoenix]

There's a how-to here - did you configure it using this guide?

[BilldaCat]

Originally Posted by phoenix

There's a how-to here - did you configure it using this guide?

That's the one. I finally got my main.cf to where it should be with some zmlocalconfig bits, and I can now send and receive mail -- but not to the mailing list.

Mail sent to the mailing list seems to just go into a black hole. Same for subscription requests .. users can use the mailman interface to sign up, but they never get notification, nor does their action get placed in the moderator queue.

When I send an e-mail to the list from a subscribed address, this is what is written to the /var/log/messages log file:

Aug 12 23:57:11 cssc amavis[5593]: (05593-03) ESMTP::10024 /opt/zimbra/amavisd/tmp/amavis-20060812T215656-05593: <billdacat@(subscribermailacct)> -> <kickball@(host)> Received: SIZE=1262 from (host) ([127.0.0.1]) by localhost ((host) [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05593-03 for <kickball@(host)>; Sat, 12 Aug 2006 23:57:11 -0500 (CDT)
Aug 12 23:57:11 cssc amavis[5593]: (05593-03) Checking: 8oMT7wWJBBEM [64.233.182.188] <billdacat@(subscribermailacct)> -> <kickball@(host)>
Aug 12 23:57:11 cssc amavis[5593]: (05593-03) FWD via SMTP: <billdacat@(subscribermailacct)> -> <kickball@(host)>, 250 2.6.0 Ok, id=05593-03, from MTA([127.0.0.1]:10025): 250 Ok: queued as 6FD93ED0670
Aug 12 23:57:11 cssc amavis[5593]: (05593-03) Passed CLEAN, [64.233.182.188] [64.233.182.188] <billdacat@(subscribermailacct)> -> <kickball@(host)>, Message-ID: <92d42e030608122158j1434b25ct7b24f6f990ef0d23@mail .(subscribermailacct)>, mail_id: 8oMT7wWJBBEM, Hits: 2.139, 437 ms
Aug 12 23:57:11 cssc amavis[5593]: (05593-03) extra modules loaded: Net/LDAP/Bind.pm


so I think it's getting delivered, but where it goes after that I can't figure out.

[rsharpe]

That is just message being scanned by the content-filters there should be some information after those log entries that involves postfix send it or dropping it or bouncing it.