[Custom SMTP Email Server] - Google SMTP - 534-5.7.9 Application-specific password required
[Custom SMTP Email Server] - Google SMTP - 534-5.7.9 Application-specific password required When using GoogleSMTP with Sisense, you might encounter an issue where emails stop being received, and the logs display the following error message: 534-5.7.9 Application-specific password required. This occurs because, if you have enabled 2-factor authentication on your Google account, you cannot use your regular password for programmatic access to Gmail. Instead, you need to generate an app-specific password to use in place of your actual password. An app password is a 16-digit code that allows a less secure app or device to access your Google Account. These passwords are only applicable to accounts with 2-Step Verification enabled. Steps: Log in to your Google account. Navigate to My Account > Sign-in & Security > App Passwords (you may need to sign in again to confirm your identity). Scroll down to the "Select App" section (within the Password & sign-in method box) and choose "Other (custom name)". Name the app password, for example, "nodemailer". Click "Generate". Copy the generated password and paste it into your Node.js script in place of your actual Gmail password. Related content: For more detailed information about Gmail SMTP errors and codes please check out this article: https://support.google.com/a/answer/3726730?hl=en Setting Up Custom Email Servers1.7KViews1like0CommentsEmail Troubleshooting
NOTE: This is an updated version of the following community article - https://community.sisense.com/t5/knowledge/email-troubleshooting-sisense-7-2/ta-p/8941 This guide will demonstrate a few official first steps for troubleshooting many of the common issues that we see with the email portion of the Sisense Application.763Views2likes0CommentsScheduled Email Randomly not sent
Are some of your scheduled dashboard reports failing to send while others go through smoothly? This guide provides essential steps to diagnose and fix the problem. Start by increasing memory limits on your Sisense pods to ensure they can handle the workload. Next, check and adjust your SMTP server settings and firewall configurations to eliminate potential bottlenecks. If issues persist, detailed logs and a support ticket may be required. Follow our step-by-step troubleshooting approach to get your email reports running seamlessly again.558Views0likes1Comment