Page 1 of 1

Zimbra | Z-Push problem

Posted: Mon Aug 13, 2018 9:16 pm
by godinicp
I'm getting error messagess in /opt/zimbra/log/zmmailboxd.out
2018-08-13 23:04:34.844:INFO:oejs.DoSFilter:qtp66233253-612:https:https://webmail.luceed.hr/service/soap/: Ignoring malformed remote address <Zimbra_IP_address>, <Z-Push IP address>
2018-08-13 23:04:34.844:INFO:oejs.DoSFilter:qtp66233253-612:https:https://webmail.luceed.hr/service/soap/: Ignoring malformed remote address <Zimbra_IP_address>, <Z-Push IP address>
2018-08-13 23:04:34.844:INFO:oejs.DoSFilter:qtp66233253-612:https:https://webmail.luceed.hr/service/soap/: Ignoring malformed remote address <Zimbra_IP_address>, <Z-Push IP address>

I have whitelisted IP address of Z-Push server as shown on https://wiki.zimbra.com/wiki/DoSFilter

2018-08-13 23:07:15,224 INFO [qtp66233253-652:https:https://webmail.luceed.hr/service/soap/] [] misc - Access from IP <Zimbra_IP_address>, <Z-Push IP address> suspended, for repeated failed login.
2018-08-13 23:07:15,572 INFO [qtp66233253-652:https:https://webmail.luceed.hr/service/soap/] [] misc - Access from IP <Zimbra_IP_address>, <Z-Push IP address> suspended, for repeated failed login.
2018-08-13 23:07:15,575 INFO [qtp66233253-652:https:https://webmail.luceed.hr/service/soap/] [] misc - Access from IP <Zimbra_IP_address>, <Z-Push IP address> suspended, for repeated failed login.
2018-08-13 23:07:15,584 INFO [qtp66233253-658:https:https://webmail.luceed.hr/service/soap/] [] misc - Access from IP <Zimbra_IP_address>, <Z-Push IP address> suspended, for repeated failed login.

Zimbra version:8.7.4_GA_1730
Z-Push version: 2.40

Re: Zimbra | Z-Push problem

Posted: Wed Sep 12, 2018 12:47 pm
by maxxer
did you manage to solve? I've the same problem, Zimbra is seeing two IPs from zpush connections

Re: Zimbra | Z-Push problem

Posted: Wed Feb 06, 2019 10:56 am
by zharky
I have the same problem. Did anyone solve it?

Re: Zimbra | Z-Push problem

Posted: Wed Feb 06, 2019 11:49 am
by maxxer
zharky wrote:I have the same problem. Did anyone solve it?

I did work around the issue by pointing zpush directly to the java port instead of using the default 443 of nginx, but still haven't had time to understand why it's behaving this way