8.0.2 Community Edition - no longer allows SMTP auth users send email - RBL blocked

[Rich Graves]

Did you reload postfix after changing the config? "zmmtactl reload" should be non-disruptive.
Sorry, ZCS 8 is still quite new -- I haven't loaded it even in test -- and this isn't the best time of year to be looking for help.

[17126thunder04]

Yep. Along with a "zmcontrol restart" and physical reboots of the server (but not for this issue).

[magneticinduction]

I have this same issue. Look at this output of zmmtactl reload. Does this give any clues? It says "unused parameter."


$ zmmtactl reload

Rewriting configuration files...done.

/opt/zimbra/postfix/sbin/postconf: warning: /opt/zimbra/postfix-2.10-20121007.2z/conf/main.cf: unused parameter: permit_sasl_authenticated=yes

/postfix-script: refreshing the Postfix mail system

Stopping saslauthd...done.

Starting saslauthd...done.

Stopping opendkim... done.

Started opendkim: pid 6401

[Labsy]

Same problem here after yesterday's upgrade to 8.0.2.

Hundreds of customers reporting, that they have been blacklisted in PBL on spamhouse.org.
Removed "zen.spamhouse.org" from Admin MTA config,

removed "add X-originating IP" option,

restarted zmmtactl
But no joy!

X-Originating-IP is still there... I mean, it is NOT enabled in config, but is added in outgoing mails.
***EDIT***

Pardon..."Add X-Originating-IP" checkbox is still checked in Admin....even after SAVE and restart, it keeps coming back.

[17126thunder04]

I was under the impression that unchecking the option for "Add X-Originating-IP" only affected those who use the Zimbra web interface. I disabled it temporarily to see if It'd help in my case and it didn't appear to...so I re-enabled it.
We actually LIKE X-Originating-IP as there are cases where determining if an email was sent from a device on our network or not is helpful. I suppose I could try disabling it again (and better verify if it truly disables since you're having trouble disabling it altogether).

[quanah]

Have you read over https://bugzilla.zimbra.com/show_bug.cgi?id=44384#c44 ?

[17126thunder04]

[quote user="quanah"]Have you read over https://bugzilla.zimbra.com/show_bug.cgi?id=44384#c44 ?[/QUOTE]
I'm not sure. I looked at something similar, but it didn't have any helpful information. This one might.
What's the best way to set amavis_originating_bypass_sa to yes so that this is persistent through upgrades?

zmlocalconfig postfix_amavis_originating_bypass_sa=yes

?

[quanah]

[zimbra@edge01-zcs ~]$ zmlocalconfig | grep amavis

amavis_originating_bypass_sa = false
So:
zmlocalconfig -e amavis_originating_bypass_sa=true

[17126thunder04]

I did a

zmlocalconfig | grep amavis

And found that it's in fact "amavis_originating_bypass_sa" and it's set to false. I is so smart. :D
Anywho, when I try to set it to another value, I get the following:

zimbra@cottontail:~$ zmlocalconfig amavis_originating_bypass_sa=true

Warning: null valued key 'amavis_originating_bypass_sa=true'

What is this n00b doing wrong?

[17126thunder04]

[quote user="quanah"]zmlocalconfig -e amavis_originating_bypass_sa=true[/QUOTE]
Of course! I have to tell it I'm editing. D'uh.
Sweet. So, would a simple zmmtactl restart apply this setting?