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

Console command that sends a simple test email #14455

Closed
mattab opened this issue May 17, 2019 · 1 comment
Closed

Console command that sends a simple test email #14455

mattab opened this issue May 17, 2019 · 1 comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented May 17, 2019

-> The goal of this issue is to create a simple console command that sends a test email. The email should have the default Matomo header and footer and just say something like Hello, world! <br/> This is a test email sent from $MATOMO_URL and subject This is a test email sent from $MATOMO_URL where MATOMO_URL is the matomo instance URL.

Why? To have a simple way to check if sending an email from CLI works. Because many people experience the problem that Scheduled email reports are not sent from core:archive crontab, while they are sent correctly when one manually clicks on Send report now button. See this example bug report https://forum.matomo.org/t/auto-archiving-no-emails-sent/32643 (there are many other similar ones). In some (all?) cases, the problem is that the emails won't send from CLI. For example because PHP CLI config is different from the apache/nginx config and there may be something (eg. sendmail) mis-configured.

A common work-around is to use a SMTP server where usually this problem goes away.

@mattab mattab added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label May 17, 2019
@mattab mattab added this to the 3.11.0 milestone May 17, 2019
@Findus23
Copy link
Member

Sounds a lot like #14302.
I'm closing this in favor of #14302 as I have cross-linked the related issues there.

@Findus23 Findus23 added the duplicate For issues that already existed in our issue tracker and were reported previously. label May 17, 2019
@mattab mattab modified the milestones: 3.11.0, 3.10.0 May 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants