Always a restart services or even entire server is done with these changes.
External won't give me results (I have no access on 465 by firewall policy)
So it is not really an important thing right now, but I would like to kill port 465 anyway internally.

Well, after installing 8.8 and now on 8.8.8 it is still active… For all I can read, this should be gone by upgrading?... I see a lot of documents where I cannot figure out if it is old or recent... 587 is also active although I don't see it mentioned in the master.cf I do see: 465 inet n - n - - smt...

Already used this to get TLSv1 disabled for the most protocols with: zmprov gcf zimbraMailboxdSSLProtocols zmprov mcf -zimbraMailboxdSSLProtocols TLSv1 zmprov gcf zimbraReverseProxySSLProtocols zmprov mcf -zimbraReverseProxySSLProtocols TLSv1 So I have TLSv1 disabled, but my monitoring software find...

I was able to view some logging, but I cannot find any logs about SMTP-connections.
Is that found elsewhere on the server? Or should that be somewhere in /opt/zimbra/log ?

Have set password for Zimbra and it works, thank you.

I am prety a noob in Zimbra, so I need to figure out which logfile to look into.
Also a Windows-guy quite a bit so I want to open those logs with WinSCP, but don't know the zimbra user password.
Not quite sure if I can just reset that password and not killing the server.

Ah, and just now delayed mail from early this morning comes in. My batchedSMTP delived it.
So SMTP has been giving problems for over 12 hours now. As I am migrating, I haven't got that much traffic jet but it will be busy once fully migrated.

That is, until I know what is bugging the system...

As I also use WinSCP to browse my Linux servers, I wanted an easy way to dig into logfiles in Zimbra. But that is not possible as the /opt/zimbra/log is owned solely by the zimbra-user. I am not that familiar with Linux just to use the password function, guessing it would screw things up bigtime. So...

I had this problem before and eventually rebooted the server but that did not fix it. After a restart of the Zimbra serivces (zmcontrol restart, cause a reboot does not work for some reason...) my eMClient mail client was able to send mail again. And today, I guess a month later, it appeared again. ...