Comprehensive Guide to Resolving SMTP Authentication Error 535-5.7.8 in Ruby on Rails

Problem Background and Error Analysis

During Ruby on Rails development, when using Gmail SMTP servers for email delivery, developers frequently encounter Net::SMTPAuthenticationError with the specific message 535-5.7.8 Username and Password not accepted. This error indicates that the SMTP server has rejected the provided username and password combination, even when the credentials are perfectly valid for web login.

Core Configuration Essentials

To successfully configure Gmail SMTP, several critical elements must be ensured:

First, verify that the Gmail account being used is valid and active. In the config/environments/development.rb file, the SMTP settings should contain accurate account information:

config.action_mailer.smtp_settings = {
  address: 'smtp.gmail.com',
  port: 587,
  domain: 'gmail.com',
  user_name: 'YOUR_USERNAME@gmail.com',
  password: 'YOUR_PASSWORD',
  authentication: 'plain'
}

It's worth noting that in some cases, removing the enable_starttls_auto: true option may help resolve authentication issues, as TLS auto-negotiation can sometimes create compatibility problems with Gmail servers.

Security Settings Adjustment

Google account security policies are a common cause of this error. Modern Gmail accounts by default block access from "less secure apps." To resolve this, visit the Less secure app access page in Google account settings and set this option to "Enabled."

In practice, some users find that even when this option is already enabled, disabling and then re-enabling it can refresh the authentication state, resolving temporary authentication failures.

Advanced Security Solutions

For security-conscious users, enabling "less secure apps" might not be the optimal choice. An alternative approach is using Google's App Passwords feature. This requires first enabling two-step verification, then generating a 16-digit app-specific password on the App passwords page.

After generating an app password, use this password in the SMTP configuration instead of the account's main password:

config.action_mailer.smtp_settings = {
  address: 'smtp.gmail.com',
  port: 587,
  domain: 'gmail.com',
  user_name: 'your_email@gmail.com',
  password: 'GENERATED_APP_PASSWORD',
  authentication: 'plain',
  enable_starttls_auto: true
}

Configuration Verification and Testing

After completing the configuration, it's recommended to test through the Rails console:

# Start Rails console
rails console

# Test email sending
ActionMailer::Base.mail(
  from: 'test@example.com',
  to: 'recipient@example.com',
  subject: 'Test Email',
  body: 'This is a test email.'
).deliver_now

If configured correctly, this test should execute successfully without throwing authentication errors.

Environment-Specific Considerations

In development environments, ensure both config.action_mailer.raise_delivery_errors and config.action_mailer.perform_deliveries are set to true, allowing immediate error visibility and rapid debugging.

For production environments, consider using dedicated email services like SendGrid or Mailgun, which offer more reliable service and better scalability while avoiding various Gmail limitations.

Conclusion

The key to resolving the 535-5.7.8 error lies in understanding Gmail's security policies and SMTP configuration requirements. By properly configuring account security settings, using appropriate authentication parameters, and considering app-specific passwords, developers can reliably solve this common authentication issue. It's recommended to choose the most suitable solution based on specific security needs and environmental requirements.