Topic: Email changing to hostname.domain.net

[Warbird30]

Not sure why, but after upgrading to SME 10, emails are going out as 'username@hostname.domain.net'.  Previously they went out as 'username@domain.net'.  The problem is that dmarc is now failing and getting the error message '550 relaying denied username@hostname.domain.net'.

[bunkobugsy]

Is this from webmail? Happened to us too. You need to set:

config setprop horde ForcePrimaryDomain enabled
signal-event console-save

[Warbird30]

Is this from webmail? Happened to us too. You need to set:

config setprop horde ForcePrimaryDomain enabled
signal-event console-save

Thanks for the reply.  Followed your directions and now for some reason it changed the address from 'user@host.domain.net' to 'user@domainnet minus the period (instead of user@domain.net). 

'db domains show' shows:

domain.net=domain
Content=Primary
Description=Primary domain

[Jean-Philippe Pialasse]

i understand the privacy but is the domain really of type
domain.tld
or rather
domain.co.tld ?

[bunkobugsy]

Oh, forgot this was patched, but not yet released, so you also need to:

yum update smeserver-horde --enablerepo=smeupdates-testing

and then again:

signal-event console-save

[Warbird30]

Oh, forgot this was patched, but not yet released, so you also need to:

yum update smeserver-horde --enablerepo=smeupdates-testing

and then again:

signal-event console-save

That made back and forth from non-webmail work without issue, but now not able to access webmail at host.domain.net/webmail.

[Jean-Philippe Pialasse]

please do

yum downgrade smeserver-horde


by doing the upgrade this way you went too far missing some new elements. 

[Warbird30]

please do

yum downgrade smeserver-horde


by doing the upgrade this way you went too far missing some new elements.

If it helps, can access webmail locally, but not remotely after the previous update and it showed as user@domain.net

[Jean-Philippe Pialasse]

here are the last fixes.


Thu May 26 2022 Jean-Philippe Pialasse <tests@pialasse.com> 1.0.0-33.sme
- fix invalid domain if ForcePrimaryDomain is enabled [SME: 11980]
- fix $ldapServer is commented out if Horde ForcePrimaryDomain is disabled [SME: 11981]

* Sun Apr 17 2022 Jean-Philippe Pialasse <tests@pialasse.com> 1.0.0-32.sme
- use httpd 2.4 access control syntax [SME: 11945]


as you see the bug you need fixed has been fixed after another one which create the issue you have to access horde. probably because you did not update smeserver-php and e-smith-apache at the same time. However they have not beem fully verified, so i do mot suggest you update all on your production server. 

[Warbird30]

here are the last fixes.


Thu May 26 2022 Jean-Philippe Pialasse <tests@pialasse.com> 1.0.0-33.sme
- fix invalid domain if ForcePrimaryDomain is enabled [SME: 11980]
- fix $ldapServer is commented out if Horde ForcePrimaryDomain is disabled [SME: 11981]

* Sun Apr 17 2022 Jean-Philippe Pialasse <tests@pialasse.com> 1.0.0-32.sme
- use httpd 2.4 access control syntax [SME: 11945]


as you see the bug you need fixed has been fixed after another one which create the issue you have to access horde. probably because you did not update smeserver-php and e-smith-apache at the same time. However they have not beem fully verified, so i do mot suggest you update all on your production server.

Thank you for that information.  I will run 'yum downgrade smeserver-horde' as you said and then change ForcePrimaryDomain to disabled.  Is there anything else I should do? Out of curiosity, is that any time frame for those fixes?

[Warbird30]

Thank you for that information.  I will run 'yum downgrade smeserver-horde' as you said and then change ForcePrimaryDomain to disabled.  Is there anything else I should do? Out of curiosity, is that any time frame for those fixes?

Well, now unable to access webmail locally or remotely after 'yum downgrade smeserver-horde'. 

[bunkobugsy]

Did e-smith-apache also get downgraded?

rpm -qa smeserver-horde
rpm -qa e-smith-apache

[Warbird30]

Did e-smith-apache also get downgraded?

Not sure. running 'rpm -qa e-smith-apache' shows
'e-smith-apache-2.6.0-19.el7.sme.noarch'

rpm -qa smeserver-horde
smeserver-horde-1.0.0-29.el7.sme.noarch

[bunkobugsy]

it didn't, please also   yum downgrade e-smith-apache
sorry for the mess I created

[Warbird30]

it didn't, please also   yum downgrade e-smith-apache
sorry for the mess I created

Webmail is now accessible locally and remotely (yeah).  It's all good, at least there is a fix in the works (and it worked locally at least).  Appreciate all the help you guys have given.  Now to go pass out as I've been up for about 20 some hrs now (crosses fingers that no one calls early..  lol).

[Jean-Philippe Pialasse]

timeframe depends on how many people work on verifying the 3 bugs and make sure no issue arise like the one you seem to see.