In my earlier blog, we saw one possible cause database mail error due to SSL settings. Today we will learn about another Database Mail Error.
SQL SERVER – Database Mail Error: The SMTP Server Requires a Secure Connection or the Client was not Authenticated. The Server Response Was: 5.5.1
Database Mail with Gmail failed: the SMTP server requires a secure connection or the client was not authenticated, 5.5.1. Here is how to fix it.
SQL Authority News – Brent Ozar Unlimited Office Hours 2018/4/4 – Fun Experience
I joined Brent, Richie and Tara for Brent Ozar Unlimited office hours and answered live questions, from replication latency to disk space. Here is the list.
SQL SERVER – sp_readrequest – Long Running Process
sp_readrequest kept showing up as a long running procedure. It is Database Mail waiting on its queue with a 600 second timeout, usually nothing to worry about.
SQL SERVER – Script level upgrade for database ‘master’ failed – There is already an object named ‘DatabaseMailUserRole’ in the database
After patching, script level Upgrade for master failed: there is already an object named ‘DatabaseMailUserRole’. Here is what caused it and how to fix it.
SQL SERVER – Stop Growing MSDB Database by Removing sysmail_mailitems History
A client’s MSDB database had grown huge from Database Mail history and was slowing things down. Here is how to clean up sysmail_mailitems and stop the growth.
SQL SERVER – Database Mail Breaks with TLS 1.0 Disabled Discovery – Notes from the Field #128
Ryan Adams sent a test email and it never arrived. He explains why Database Mail breaks when TLS 1.0 is disabled and how he tracked down the cause.