[SOLVED] Change default milter server bind port

[liveaverage]

Good morning,

Just upgraded to version 7.0 from 6.0.8 and I was wondering how to change the default milter server bind port? I tried searching the forums and wiki but couldn't seem to find anything. I'm assuming this a zimbra-configured option since any manual settings to the postfix main.cf file get overwritten each time I attempt a reload on the MTA -- not a big deal, and I'm a bit excited I won't have to manually change the postfix configuration after each upgrade :-)

I've temporarily changed the port on our MailArchiva server (from 8092 to 7026) so we can still archive, but I'd like to know how/if I can change that port setting.

Everything else looks and performs great with the upgrade!

>JR

[phoenix]

How about comment #19 on the bug report: Bug 8791 – make support for postfix-policyd easier

[liveaverage]

Is that related to the milter server bind port, or just cluebringer bind port? I was just hoping to change the milter server bind port (if possible). Again, not high priority since I changed listener port on the archiving server, but it'd be nice to know how to change it if it's possible Is it possible with the zimbra CLI already, or does it relate to the reported cluebringer bug?

Thanks for the quick reply!

[liveaverage]

Well, of course I find the attribute after the fact, but....

Verify the milter bind port:

zmprov gs mail.server.com zimbraMilterBindPort

Should return the default 7026

Modify the milter bind port for MailArchiva (8092):

zmprov ms mail.server.com zimbraMilterBindPort 8092

Make other changes directly to the main.cf file and restart MTA:

zmmtactl restart

[lytledd]

Just to add to this, for those with MailArchiva on a different machine:

zmprov ms mail.server.com zimbraMilterBindAddress ip.address

Doug

[leep75]

Originally Posted by lytledd

Just to add to this, for those with MailArchiva on a different machine:

zmprov ms mail.server.com zimbraMilterBindAddress ip.address

Doug

Can you elaborate on this more? I'm trying to get mailarchiva working again after upgrading from ZCS 6.0.10 to 7.01 this morning. I can't get it to work. My mailarchiva is on a different box. I've tried all options in this thread (as well as several other things found on the Internet).

Thanks
AL

[lytledd]

Originally Posted by leep75

Can you elaborate on this more?

Lets say my server is domain.com and MailArchiva is on 10.0.0.11, I did the following:

zmprov ms domain.com zimbraMilterBindAddress 10.0.0.11
zmprov ms domain.com zimbraMilterBindPort 8092

zmmtactl restart

Doug

[leep75]

Originally Posted by lytledd

Lets say my server is domain.com and MailArchiva is on 10.0.0.11, I did the following:

zmprov ms domain.com zimbraMilterBindAddress 10.0.0.11
zmprov ms domain.com zimbraMilterBindPort 8092

zmmtactl restart

Doug

That's what I thought. I tried that and I added the line:
milter_default_action = tempfail

above the smtpd_milters = line in /opt/zimbra/postfix/conf/main.cf

However, now when I check the main.cf there is no mention of my mailarchiva server ip 192.168.0.13 or the port 8092.

Before running those commands should I login to my admin console and check the box to enable milters?

[lytledd]

Yes,

I had to do that as well. Also note, the web admin console will show the incorrect port, even after updating.

Doug

[leep75]

Originally Posted by lytledd

Yes,

I had to do that as well. Also note, the web admin console will show the incorrect port, even after updating.

Doug

Thanks for the help. I think it's finally working. However, I do have one strange issue. When I enabled the milter service and ran zmmtactl restart
on the admin console the "MTA" is displaying a red X, however, I am sending and receiving mail both inside and outside my network. Any ideas on this?


****UPDATE*****
I did a zmcontrol stop && zmcontrol start and that seemed to fix the red x. All is well! Thanks for the help.