No need to re-run the postmap command then, just use - to remove? Also, do you know why this did not work? The only way I was able to r eceive the email from that domain was by adding it's IP like this; zmprov ms mx.unrealmachines.com zimbraMtaMyNetworks 'x.x.x.x/32 This seems to be the wrong way a...

Hello, I think that you could remove it just changing the operator ( - zimbraMtaRestriction): zmprov mcf -zimbraMtaRestriction 'check_client_access lmdb:/opt/zimbra/conf/postfix_rbl_override' The sender was blocked due to a HELO restriction. It would be a "check_helo_access" instead of &qu...

Hello Joao,

Please check this blog:

https://respirandolinux.com.br/2018/10/ ... erao-2018/

HI guys,

Zimbra support is still analysing this issue. I've exported our SQLite database and sent to them.

As soon as I get an update I will share with you guys.

Best regards.

Hello guys,

Thanks for sharing my post here. I've updated it with the rule file to fix events created before the fix:

https://respirandolinux.com.br/2018/10/ ... erao-2018/

DavidMerrill wrote:Anything interesting back from Zimbra Support on this?

Hello David,

Thank you for the attention. This case is being well handled by Zimbra support team.

Best regards.

Hello,

Yes, it does work pretty well for us.

What client are you using?

Hello,

Please take a look at this Zimlet:

https://zimbra.org/extend/items/view/zi ... ox-toolkit

Hi,

Please check the zimbraMailboxdSSLProtocols parameter:



I did not test it, but I think you could simply add TLS v1.3 to it:



Best regards.

Hi Miguel,

Take a look at this documentation: https://wiki.zimbra.com/index.php?title ... eployments

I would recommend to search for "Memory Allocation" and read about mailboxd_java_heap_memory_percent and mailboxd_java_heap_size.

Best regards.