after modifying zimbraMailTransport - what to restart w/o zmcontrol stop/start?

[gettyless]

I was about to submit this:

I'm about to do a split domain migration with zimbra as primary MTA. I'd prefer to not take down my whole server with a "zmcontrol stop && zimcontrol start" when I migrate each use over time.

I guess it's one of these?

zimbra@zimbra:~/bin$ ls *ctl*
zmamavisdctl	zmauditswatchctl  zmmailboxdctl   zmproxyctl	  zmswatchctl
zmantispamctl	zmclamdctl	  zmmemcachedctl  zmsaslauthdctl  zmtlsctl
zmantivirusctl	zmconvertctl	  zmmtaconfigctl  zmspellctl	  zmzimletctl
zmapachectl	zmloggerctl	  zmmtactl	  zmstatctl
zmarchivectl	zmlogswatchctl	  zmnginxctl	  zmstorectl

http://wiki.zimbra.com/index.php?title=Split_Domain doesn't mention it.

... and the answer is: [No nevermind this is totally wrong, don't need to do this.]

"/opt/zimbra/bin/zmmtactl reload" which will output.

I'll add this to the wiki.

[gettyless]

oops nevermind. the Split Domain wiki page is "certified". So whoever has permissions for it, I think you should add in this info.

It might might apply to all cases but I think it's worth mentioning.

[sreeharsha.t]

Hi,
Is the reload really needed. I too tried this Spilt Domain configuration and when I added users on zimbra and changed zimbraMailTransport LDAP attribute, the mail worked out without a restart or reload..

[gettyless]

Actually you're right - I'm going through a migration of some accounts right now and and I just have to set zimbraMailTransport.