0

I'm running Buster and use SMTP to send emails from the command line and it works just fine.

When I try to send emails using Python it fails miserably, I've tried various python examples from the net, e.g.

# Sending Email Alerts via Zoho # # import smtplib server = smtplib.SMTP_SSL('smtp.zoho.com',port=465) #server for sending the email server.ehlo() # simple starting of the connection server.login('[email protected]','pwd_12345') # login credentials and password msg = """From:[email protected] Subject: Test Email \n To: [email protected] \n""" # This is where the email content goes. It could be information about the error, time of day, where in the script, etc. server.sendmail('[email protected]','[email protected]',msg) # this is where the email is sent to the recipient server.quit() # exit the connection 

.. but I unfortunately I always get the following error:

Traceback (most recent call last): File "/usr/lib/python3.7/smtplib.py", line 387, in getreply line = self.file.readline(_MAXLINE + 1) File "/usr/lib/python3.7/socket.py", line 589, in readinto return self._sock.recv_into(b) ConnectionResetError: [Errno 104] Connection reset by peer 

As a newbee any hint would be appreciated.

Thanks!

0

2 Answers 2

1

This could be a server/firewall configuration issue vs a programming issue. You need to verify that you can send an e-mail through the same server to the same destination via other means from the same device.

Sign up to request clarification or add additional context in comments.

2 Comments

For instance, you could follow the SMTP testing instructions here: port25.com/… If you get a connection reset error from your telnet client, that would confirm the problem lies elsewhere.
This issue has been solved! My ISP uses SSL on port 465 and my command line email client MSMTP works just great using that. As I was so desperate, so that I startet to play around and just use port 25 and "Bingo" sending of emails works now just fine, the funny part is that my ISP suggest to use port 465.
0

This issue has been solved!

My ISP uses SSL on port 465 and my command line email client MSMTP works just great using that.

As I was so desperate, so that I startet to play around and just use port 25 and "Bingo" the email notifications work now just fine, the funny part is that my ISP suggest to use port 465.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.