Hello folks,
Do you know if there is a fix for this problem yet?
Sorry if this is considering "necroposting".
Regards
Search found 7 matches
- Thu Feb 01, 2018 12:12 am
- Forum: General Questions
- Topic: rendering issue
- Replies: 16
- Views: 25924
- Tue Aug 29, 2017 10:35 pm
- Forum: Administrators
- Topic: [SOLVED] /opt/zimbra/bin/zmshutil: line 41: export: `antispam_enable_rule-updates=true': not a valid identifier problem
- Replies: 1
- Views: 2919
Re: /opt/zimbra/bin/zmshutil: line 41: export: `antispam_enable_rule-updates=true': not a valid identifier problem
Hello Mr. Boopathiraja,
I had the same problem, it's a wrong key in the /opt/zimbra/conf/localconfig.xml file.
You should edit the xml by yourself.
This thread gave me the answer.
Hope you had fun this 2 years of waiting for an answer
Regards
I had the same problem, it's a wrong key in the /opt/zimbra/conf/localconfig.xml file.
You should edit the xml by yourself.
This thread gave me the answer.
Hope you had fun this 2 years of waiting for an answer
Regards
- Wed Jun 08, 2016 8:38 pm
- Forum: Administrators
- Topic: error in network service after one wrong login
- Replies: 13
- Views: 12806
Re: error in network service after one wrong login
It's OK, I took a deeper look to the logs and found out that AcceptSecurityContext error, data 531 is a AD-specific error code which means "not permitted to logon at this workstation". So the users we're restricted to the station were they can login and my zimbra server wasn't one of those...
- Fri May 20, 2016 1:41 am
- Forum: Administrators
- Topic: error in network service after one wrong login
- Replies: 13
- Views: 12806
Re: error in network service after one wrong login
Hello Folks, I also got a similar problem with LDAP Auth. AFAIK is not related to DoSFilter (No other messages from this module show up) 2016-05-19 19:36:03,142 INFO [qtp509886383-5376:http://127.0.0.1:80/service/soap/AuthRequest] [name=account@domain.com.ni;oip=192.168.1.204;ua=zclient/8.6.0_GA_115...
- Thu Feb 09, 2012 2:28 pm
- Forum: Administrators
- Topic: [SOLVED] Postfix won't start after upgrade to 7.1.3
- Replies: 8
- Views: 3667
[SOLVED] Postfix won't start after upgrade to 7.1.3
I migrated my server into a new one and got the same mistake.
Feb 9 14:29:23 mail postfix/smtpd[17340]: fatal: host/service 127.0.0.1/None not found: Servname not supported for ai_socktype
Any idea?
Feb 9 14:29:23 mail postfix/smtpd[17340]: fatal: host/service 127.0.0.1/None not found: Servname not supported for ai_socktype
Any idea?
- Wed Feb 08, 2012 2:35 pm
- Forum: Administrators
- Topic: [SOLVED] Postfix won't start after upgrade to 7.1.3
- Replies: 8
- Views: 3667
[SOLVED] Postfix won't start after upgrade to 7.1.3
Thanks for the reply phoenix, I already tried with ipv4 and the result is the same.
I found in some searches this kind of error in ntp configuration but this one is not showing which is the service. Any idea?
I found in some searches this kind of error in ntp configuration but this one is not showing which is the service. Any idea?
- Wed Feb 08, 2012 12:28 pm
- Forum: Administrators
- Topic: [SOLVED] Postfix won't start after upgrade to 7.1.3
- Replies: 8
- Views: 3667
[SOLVED] Postfix won't start after upgrade to 7.1.3
Since I upgraded a while ago I have the same issue with the postfix conf file (main.cf): Starting mta...Failed. postalias: fatal: bad string length 0 postfix failed to start I did what camunai suggested and now I got this on my zimbra.log when tried to start postfix manually Feb 8 11:01:21 mail post...