Emails not being sent

[ChinookTx]

I can't get EmailNotifier to send emails upon completion of prints. Nothing happens. Checking the mail server logs, it does not even appear to be trying. Is authentication required? I have a postfix server running on the same lan as my printers, and it is not protected (no login required). Telnet'ing to port 25 on the mail server and entering the commands works. Is there a way to test the emails from the plugin?

[anoved]

Thanks for the report. I know this plugin needs an update. It should be considered a work in progress that was probably added to the repository prematurely. (Sorry.)

To answer your question, since the plugin uses yagmail to send email, you might test some of the examples from the yagmail readme directly on your octoprint system.

[cmtec]

I have this issue as well.

I might be wrong but it seems that yagmail defaults to gmail port (port='587') when creating the yagmail instance and this plugin do not pass the port as an argument and therefor i guess this plugin only work with gmail right now.

Is it possible to add an port input field for custom/non gmail ports?

[ChinookTx]

After looking through the code, it will not support "non password" methods, for example if you have your own SMTP server, etc. I believe it will also default to port 587, so unless this is what you are using, it will not work. I have modified the plugin to use plain SMTP on port 25 (no auth, no SSL, nothing) and it has been working ok for me. I don't know how to package it to publish it on github though.

…

On Thu, Jan 5, 2017 at 3:42 AM, Christoffer Martinsson < ***@***.***> wrote: I have this issue as well. I might be wrong but it seems that yagmail defaults to gmail port (port='587') when creating the yagmail instance and this plugin do pass the port as an argument and therefor i guess this plugin only work with gmail right now. Is it possible to add an port input field for custom/non gmail ports? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTF29zFBOBjpmimGGh8dqqtzkGvZV1Eks5rPK0SgaJpZM4LIJWC> .

-- Patrick Brochu

[anoved]

In lieu of publishing your version as a fork on GitHub, feel free to simply post [the relevant parts of] your code in reply here for the benefit of anyone trying to use the plugin with a similar email setup.

[intensite]

I too would love a simple SMTP transport (not gmail), please post the changes if you can. I would like to give it a shot, I am experienced in javascript but a total newbie in Python.

[ChinookTx]

I have moved away from using this plugin and therefore don't have the changes anymore. It is really easy to change the existing code to use the regular SMTP transport with SMTPLib in Python. I'll try and set it up again tomorrow, but from what I recall it was a 2-3 line change thing.

…

On Fri, Apr 21, 2017 at 9:10 PM, intensite ***@***.***> wrote: I too would love a simple SMTP transport (not gmail), please post the changes. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTF26d1qSyYv26emzLhpkUgVASEnBbSks5ryVN6gaJpZM4LIJWC> .

-- Patrick Brochu