mailserver | : warning : UNMAINTAINED - Simple and full-featured mail | Continuous Deployment library

Try setting SaveOptions to "0" instead of to zero.

Dimly in the far back reaches of my mind, something is telling me that it should be a text value.

Also, I think you should be doing this before you open the UIDocument for editing, but that's an even more dim memory.

I found the solution myself. Maybe somone can make use of it:

The code above was not false to my knowledge. The actual reason was, that I should not have used a token acquisition with client credentials but only with username/password and client id.

I am not sure if JavaMail supports this because in the documentation I could not find anything about it. The rare examples about this are usually with client credentials.

As you can see above, no AUTH command was triggered because I had not the permission to do it obviously.

What I needed to do aswell was to use the Microsoft Graph API not only to aquire a token via "password/username provider" (this type) instead of the "client credential provider" (link) but also to actually trigger a send mail command via Microsoft Graph API (link).

The client credential provider was in my case not sufficient because the admin had not specified permissions to send mails.

Thus, I didn't use JavaMail anymore for this and needed another token acquisition provider.

Solution for this issue is to make false for readonly instead of true

If you take a look at the SmtpClient.cs reference source, in the Initialize() method:

• if port == 0
  • if there is a MailConfiguration XML file available, it uses the specified port from the XML (which defaults to port 25): https://referencesource.microsoft.com/#System/net/System/Net/Configuration/SmtpNetworkElement.cs,e4c99455ef3ea37c
  • else if there is no XML config file, it uses the static defaultPort member, which is set to 25.

So to get the same behavior as System.Net.Mail, use port 25.

MailKit will also accept port = 0 in the Connect() call and, depending on what the SecureSocketOptions argument is, it will choose an appropriate default port in the ComputeDefaultValues() method: https://github.com/jstedfast/MailKit/blob/master/MailKit/Net/Smtp/SmtpClient.cs#L1253

If the port == 0, then if useSsl=true or socketOptions=SslOnConnect, it will choose port 465, otherwise it will choose port 25.

When you are writing a script for your monitoring, add functions for additional functionality, like:

• logging all the alerts that have been send
• make sure you don't send more than 1 alert each hour
• consider sending warnings only during working hours
• escalate a message when it fails N times without intermediate success
• possible send an alert to different receivers (different email adresses or also to sms or teams)
• make an interface for an operator so he can look back when something went wrong the first time.

When you have control which messages you send, it is easy to filter duplicate meassages (after changing --since).

SMTP have 2 different ports PORTS for SSL 465 PORTS for TLS/STARTTLS 587 did you try with another ports ?

TLS connection to smtp.gmail.com isn't working

Contrary to this claim TLS is working. The TLS upgrade is successful, otherwise further communication would not be possible at all. But HELO after the TLS upgrade works as expected and yields "250 smtp.gmail.com at your service".

What is wrong though is the login process. It fails to send a b"\r\n" after the base64 encoded username and password. This causes the connection to hang since the server expected more data before sending a response back.

I figured it out:

There was an IEmailSender interface within:

Run this command on your console