Hopefully 8.5.1 or 8.6.0
Type: Posts; User: quanah; Keyword(s):
Hopefully 8.5.1 or 8.6.0
Ah, I see you said you're using the transport maps. That seems like the correct method to me for what you're trying to do.
Specifically, what postconf attributes are you editing? ;)
Also, we ran out of time to fix this for 8.5, too. :(
mail routing in 8.0.3 was horribly broken. "working" is a relative term
No one has ever requested the ability to customize that field, so there's currently no key for configuring it. Please file a bug in the Zimbra bugzilla, with a specific use case, under the ZCS/ MTA...
The GIT repo system has been restructured to have all branches contained together inside a single repo. This allows correct change tracking and the ability to cherry pick between branches, among...
Port 465 is always enabled on ZCS installations as is 587. You would have to go out of your way and do all sorts of unsupported hacks to disable it.
I had to take the server offline for a few days for a project I'm working on. Hopefully that won't be necessary again. ;)
I realized since you upgraded an actual node with that value set, it is set at the server level rather than the global level.
zmprov gs `zmhostname` zimbraMtaSmtpSaslPasswordMaps
It looks like the bind dn for your external auth config got lost. May want to review LDAP Authentication - Zimbra :: Wiki
You should just upgrade. You will lose everything otherwise.
It sounds like you've broken the update function for SA, that's unfortunate. How to enable rule updates is documented at SpamAssassin Customizations - Zimbra :: Wiki
If you'd simply followed...
It's really bad form to post to a thread that's been dead for 4 years... Much more productive to start a new one.
There are numerous options you can use in ZCS8 for having postfix block a variety of failures:
The openssl updater is discussed here as a supported Zimbra tool for updating openssl:
Yes, it's a known issue that the documents on the website are wrong. I've been trying to get our website team to update them since April with no luck.
Again, there's something wrong with your...
It shouldn't be set that high because numerous sites have misconfigured SPF domains. If you did what I said, and read up on the issue, you'd understand this. So by marking SPF failures with such a...
Interesting, I've never heard of anything like that. You'd need to provide more detailed information about the errors being received.
The "principal" field is clearly wrong. The zimbra admin user DN is not uid=zimbra,ou=admin
Also, I'd say it is generally ill advised to publicly paste the password for your zimbra admin user, as...
Don't set SPF_SOFTFAIL so high. If you have questions on why SPF scoring is so low, I suggest you read the spamassassin user's list archive, it's discussed there in significant detail.
You want to disable receiving email from external sites? I suppose you could, but that means you won't get much email.
basedn is ""
By default, anonymous access to 389 is not allowed, so you also have to specify a bind dn & password if you want access.
You don't note what version of Zimbra you're running... Apache, PHP, etc get updated in new releases of ZCS. Also, vulnerability scanners are of extremely limited use, as they don't have the context...
As I stated previously, the variable has been moved from localconfig to LDAP. That means you need to use zmprov, not zmlocalconfig. You should never modify zmconfigd.cf.
"VAR" means the value is...