Subversion Repositories SmartDukaan

Last modification

• Rev 37451 2026-08-29 07:24:19
• Author: amit

• Log message:

  Send authenticated mail as the account that actually authenticates
  
  googleMailSender logs in to smtp.gmail.com as sdtech@smartdukaan.com, but callers
  build their From as noreply@smartdukaan.com. Google Workspace binds an authenticated
  session to one identity and refuses the mismatch with 535 'Authorization failed:
  Authenticated user is not authorized to send mail' - the password is accepted, the
  message is not. Every alert routed through that sender was therefore lost at the SMTP
  layer, the e-invoice failure alert for NSUPHR1770 among them.
  
  AuthenticatedIdentityMailSender rewrites From to the sender's own username at send
  time, keeping whatever display name the caller chose. Senders that do not authenticate
  are left alone: gmailRelaySender is the IP-authorised relay and has no username, and
  sendGridMailSender's username is the literal 'apikey', so both keep noreply@.
  
  Enforced in the sender rather than at the ~40 call sites that build their own
  MimeMessage and hardcode noreply@, so it covers the ones added next too.