today i upgrade my server to version 6.0.5
i waited because i had the following bug Bug 41213 – Upgrade from 5.0.18 to 6.0.0 breaks external pop / spop
and now i found a new :-( !!!! so now i use my
i use zimbra for two years and every update turns me, mostly, into another bug. (i should thinks about to change the mailserversoftware)
did anybody open a bug or found a solution? i reproduce the bug simply in installing a fresh server and add a "Allow sending email from" right to one user and send over it.
41213 is (supposedly) fixed in 6.0.5, are you saying that you are still seeing it there? Or some other bug related to "Allow sending email from", by which I am assuming you are talking about "Allow sending email from any address" in the admin console?
41213 is fixed but now "Allow sending email from any address" didn't worked for me, like in the other replies you see above.
this option you can set from the admin console (web ui from port 7071 by default).
did anybody opened a bug for this request?
I have exactly same problem. Created domain an "A" domain then added alias for "B" domain. Created user on "A" domain, added persona with "B" domain address, sending out email from "B" persona, and relay(smart host) reports that message was sent from "A" domain, on recipients end the message has correct From header but Return-Path still points to "B" domain no matter what.
did you found a solution?
i updated the bug:
today i installed zimbra open source edition 6.0.6 and i have still the same problem :-( its really annoying that i can't update from 5.0.18 to the current release.
on my testmachine i tested it with a fresh 6.0.6 installation von centos 5.4
I have the same problem. I`m following the instructions from bug#44542 to solve this problem, but when I try to set zimbraSmtpRestrictEnvelopeFrom to FALSE it gives me the error "ERROR: service.INVALID_REQUEST (invalid request: LDAP schema violation: [LDAP: error code 65 - attribute 'zimbraSmtpRestrictEnvelopeFrom' not allowed])"
I use version 6.06 on debian lenny
Are you trying to set it on a domain? This attribute is only allowed on objects of the following classes:
It would be disallowed (and give that error) on any other object class.
There are currently 1 users browsing this thread. (0 members and 1 guests)