[Users] zimbraAllowAnyFromAddress does not affect MTA

[Malte S. Stretz]

Hi Barry,

I'll do so once I verified that the instructions actually work since the 
forum post claims they don't. I know that we have some internal 
documentation somewhere on how to set this up since the Wiki pages are 
indeed quite confusing. I am sure that this worked without adding an 
extra Milter as the linked blog post does.

Cheers,

Malte


On 16.11.2017 09:39, Barry de Graaff wrote:
> Hello Malte,
>
> Yes, but it would be nice if Zimbra took care of that for us,
> as this wiki page gives me a headache :-p
>
> Could you add your comment to the bugzilla?
>
> Kind regards,
>
> Barry de Graaff
> Zeta Alliance Founder
> zetalliance.org | github.com/Zimbra-Community
>
> +31 617 220 227
> Fingerprint: 97f4694a1d9aedad012533db725ddd156d36a2d0
>
> ----- Original Message -----
> From: "Malte S. Stretz" <mss at msquadrat.de>
> To: "Barry de Graaff" <info at barrydegraaff.tk>, users at lists.zetalliance.org
> Sent: Thursday, November 16, 2017 9:36:08 AM
> Subject: Re: [Users] zimbraAllowAnyFromAddress does not affect MTA
>
> Hi,
>
> you mean that setting zimbraAllowAnyFromAddress should set the options
> documented in
> https://wiki.zimbra.com/wiki/Enforcing_a_match_between_FROM_address_and_sasl_username_8.5?
> Generally a good idea since applying those settings is a bit obscure.
>
> The problem here would be backwards compatibility. People upgrading
> Zimbra would suddenly maybe not be able to continue their normal work
> flow (and I'd get the support calls from disgruntled customers). I think
> a better solution would be an extra attribute
> zimbraMtaAllowAnyFromAddress which defaults to FALSE but is set to TRUE
> on upgrades of existing installations so the old behavior is kept. Maybe
> it could also fall back to the value of zimbraAllowAnyFromAddress if
> unset (if that's possible, not sure). There would also be an upgrade
> step required which checks if the old way of configuring this settings
> was applied before and if that's the case, the old config is removed and
> the attribute set to TRUE on upgrades as well.
>
> Cheers,
>
> Malte
>
>
> On 16.11.2017 09:09, Barry de Graaff wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Hello All,
>>
>> I think a lot of you already know this, but I think it is a
>> bit peculiar in todays age.
>>
>> The setting of zimbraAllowAnyFromAddress only removes the option from
>> the UI to set a custom FROM address. It does not seem to have any effect on the MTA.
>>
>> (zmprov gc default zimbraAllowAnyFromAddress)
>> The default setting is false, but Zimbra still accepts and delivers mail with any
>> FROM address if a user is authenticated.
>>
>> Not sure if forcing a correct FROM is a feature of Zimbra, if not, should we
>> make this is a feature request?
>>
>> https://forums.zimbra.org/viewtopic.php?t=62676
>> https://bugzilla.zimbra.com/show_bug.cgi?id=108036
>>
>> Kind regards,
>>
>> Barry de Graaff
>> Zeta Alliance Founder
>> zetalliance.org | github.com/Zimbra-Community
>>
>> +31 617 220 227
>> Fingerprint: 97f4694a1d9aedad012533db725ddd156d36a2d0
>> -----BEGIN PGP SIGNATURE-----
>> Version: OpenPGP.js v2.5.12
>> Comment: https://openpgpjs.org
>>
>> wkYEAREIABAFAloNR8wJEHJd3RVtNqLQAAD7UwCbB/gXh/HQi7GF66ccl+iP
>> +ptDTwIAn3PfS0bqeN6U1KHASs/b1CsZq7Wm
>> =s7BD
>> -----END PGP SIGNATURE-----
>>