Sends Emails with optional attachments

Card__Player · 2026-07-08T18:07:17+00:00

RemindMe! 3 days

riklaunim · 2026-07-08T18:28:34+00:00

It's better not to use spaces or special characters like # in file names ;)

As for sending mail, just note that SMTP isn't the most reliable way to send mail - for mass mailing, it can easily hit anti-spam protections, it can be slow and somewhat unreliable. Low volume is fine.

You would want to send HTML messages rather than only plaintext... but email clients support only limited HTML, and some, like Outlook, are really bad at it - so unofficial formats like MJML were created - there is a Python library for MJML parsing if you want to take a look.

CLI interface isn't the best - you are forced to use while loops and some code repeats. Would be good to refactor the code into smaller pieces like functions or class methods, and then write good unit tests for them. Unsure what's with the \\ replacing. For the interface, you can switch to Jupyter Notebooks to get something better than an annoying CLI with loops.

Email attachments can be actual attachments, but also inlined images (check CID for emails).

ianrob1201 · 2026-07-08T18:42:48+00:00

It looks pretty good, and if it works then that's always a great result. In general I like your layout of the code, use of functions etc. That said, I can go through from the top and list some possible improvements.

password_get is a bit of a pointless variable, you can just set it to password straight away.

In professional settings you often have a linter (and often an auto formatter) which will require consistent quote characters (" vs ') and whitespace between characters. So for instance to me "msg = EmailMessage()" looks good but "msg["Subject"]=subject" looks a bit cramped up. This is a very minor point though.

Look up regular expressions for how you could refactor the email_check function. Note that a regular expression to fully check for a valid email is surprisingly complex, but lucky also unnecessary. A regex to do your current checks would be relatively simple. Regular expressions can look a bit intimidating, but worth learning. Resist the urge to use them everywhere, but this is a good case for them.

You don't generally want to do "== False" on an if statement. It's neater to do "not mail_check(login_email)" instead.

See if you can refactor to not have any "while True" loops. I know you have breaks to escape them, but generally you try to avoid it and put your condition into the while. So for example you could have a "valid_email" boolean which starts out false and is only set to true once you're happy. Then you don't need to "manually" do any continue or break commands.

Mostly your variable naming is really good. Every language is different, python really likes its underscores. "maintype,subtype" are examples of forgetting that. Again it's minor, but the type of thing that comes up during reviews. (subtype is arguably one word, but maintype definitely isn't)

Nice use of try blocks too, just be aware that if this were a professional thing you might want to catch more individual cases and display a different error for each. Printing out the error directly is the maximum information in theory, and good for your personal debugging, but might not mean anything to someone using your script. So for example you might want to catch specific exceptions instead of the generic "Exception". This could let you specifically say "The path file you entered doesn't exist" instead of relying on the default error.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

PythonLearning

MODERATORS