@myfirstnameispaul opened this Issue on July 17th 2015

With Email server settings in the dasboard selected to not use SMTP server, Piwik uses the subdomain in the header.from field (e.g. noreply@www.example.com), making all emails from Piwik spam since this doesn't jive with the domain's DNS records.

I see in .../piwik/config/global.ini.php noreply_email_address = "noreply@{DOMAIN}" but I don't see where to set {DOMAIN].

I would think that adding the subdomain to the from.header address would create problems for lots of users, but maybe I have something misconfigured somewhere?

@tsteur commented on July 20th 2015 Owner

I think everyone is supposed to change noreply_email_address which is not really the best solution. You have to replace everything, the {DOMAIN} cannot be configured manually. Ideally we would replace the domain maybe with a trusted host.

@myfirstnameispaul commented on July 20th 2015

How many users know to go into global.ini.php and change this? Will Piwik overwrite that file after I make changes to it?

@tsteur commented on July 21st 2015 Owner

How many users know to go into global.ini.php and change this?

I reckon pretty much nobody does it. That's why I meant we need to improve this.

Will Piwik overwrite that file after I make changes to it?

You have to make the change in config/config.ini.php which will not be overwritten. global.ini.php will be overwritten on the next update.

@myfirstnameispaul commented on August 2nd 2015

@tsteur Sorry, I think I misread your first message when I replied.

Setting noreply_email_address = username<a class='mention' href='https://github.com/example'>@example</a>.com in config.ini.php has solved the issue, however, it appears a different parameter is set for the password recovery emails, as that is sent from password-recovery<a class='mention' href='https://github.com/www'>@www</a>.example.com.

@tsteur commented on August 6th 2015 Owner

That's a bug then. Probably {DOMAIN} should be replaced but isn't

@tsteur commented on August 6th 2015 Owner

refs #7445 maybe it's even a duplicate

Powered by GitHub Issue Mirror