-
Notifications
You must be signed in to change notification settings - Fork 315
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
Mist sends invalid requests to SMTP mail server #1028
Comments
Hi @davidrylance we looked into this and it seems there are several issues leading to the problem.
To alleviate these issues:
Thanks for bringing this up to our attention. These issues will be fixed on our next release! |
Thank you very much @dimgal1 for resolving the problem. Looking at variables in https://github.com/mistio/mist.api/blob/master/src/mist/api/config.py Could you please tell if I also need to override other Like this: MAILER_SETTINGS = {
'mail.host': "192.168.1.25",
'mail.port': "25",
'mail.tls': False,
'mail.starttls': False,
'mail.username': "",
'mail.password': "",
}
EMAIL_FROM = "[email protected]"
EMAIL_ALERTS = "[email protected]"
EMAIL_REPORTS = "[email protected]"
EMAIL_INFO = "[email protected]"
EMAIL_SALES = "[email protected]"
EMAIL_SUPPORT = "[email protected]"
EMAIL_NOTIFICATIONS = "[email protected]"
EMAIL_ALERTS_BCC = ""
NOTIFICATION_EMAIL = {
'all': "[email protected]",
'dev': "[email protected]",
'ops': "[email protected]",
'sales': "[email protected]",
'demo': "[email protected]",
'support': "[email protected]",
} Thank you. Kind regards, David |
Yes, you can override these variables too. They are used as sender email accounts and depending on your mail server configuration they may not work with the default values |
Thank you @dimgal1 . I can confirm that Now I get a lot of e-mails about "Could not fetch old counter' and "Could not send metering data". docker-compose.override.yml was applied since I can see new containers after compose up:
But the containers don't seem to work properly since I get those error e-mails. |
|
Hi @davidrylance, it will probably be easier to investigate this issue in real time. Would it be possible to arrange a quick call and look into it? If not, we can stick to this ticket. |
Dear Mist maintainers,
Thank you for Mist. It's great!
I host my own e-mail server (postfix) and I noticed that after I create an account for Mist and configure Mist to use it, the server is literally flooded by requests that generate a lot of warning logs.
I was thinking maybe there is something wrong the mail server hosted on public internet so I installed Postfix into a container on private LAN and configured it with no authentication to relay e-mails to public mail server and I see the same error logs.
Reproduce
Configure Mist e-mailing - in my case postfix on private LAN:
Or to use mailserver on public internet
./bin/adduser --admin '[email protected]' --password ...
Btw. e-mails work - I tested adding rule to mail myself when a VM is stopped / started and I get e-mails. It just something else Mist does that is wrong.
Thank you.
Kind regards,
David
The text was updated successfully, but these errors were encountered: