Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

header.from using subdomain in emails. #8372

Open
myfirstnameispaul opened this issue Jul 17, 2015 · 6 comments
Open

header.from using subdomain in emails. #8372

myfirstnameispaul opened this issue Jul 17, 2015 · 6 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc.

Comments

@myfirstnameispaul
Copy link

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
Copy link
Member

tsteur commented Jul 20, 2015

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
Copy link
Author

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
Copy link
Member

tsteur commented Jul 21, 2015

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
Copy link
Author

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

Setting noreply_email_address = username@example.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@www.example.com.

@tsteur
Copy link
Member

tsteur commented Aug 6, 2015

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

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Aug 6, 2015
@tsteur
Copy link
Member

tsteur commented Aug 6, 2015

refs #7445 maybe it's even a duplicate

@mattab mattab added this to the Short term milestone Sep 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

3 participants