title: How can I modify the return-path in a google workspace account that has the capability to send as another workspace account?
body: <p>I haven't been able to find an answer to this, so forgive me if it's been asked somewhere before.</p>
  <p>I'm working with non-profit who has a google workspace for non profits account.  I'm working on getting our SPF/DKIM/DMARC records set up, and they work perfectly except for one situation.</p>
  <p>We have two different domains, whedoncon.com, and thehellmouth.org.  Some of our users have an email on both domains (i.e. user@whedoncon.com and user@thehellmouth.org are going to the same person).  I can send emails individually from each domain, and they pass SPF, DKIM, and DMARC fine.  The problem comes in when I set up the domains to be able to send from each other.</p>
  <p>I've added the capability for user@whedoncon.com to be able to send mail as user@thehellmouth.org.  The issue seems to be when I log in as user@whedoncon.com, and send a message as user@thehellmouth.org.  Looking at the email headers, it seems that because I logged in as user@whedoncon.com, it sets the return-path to the whedoncon.com address regardless of what account I select to send out the email.</p>
  <p>The problem with this, is it causes DMARC to fail whenever I send an email out as user@thehellmouth.org, even though SPF and DKIM both pass.  It seems to be because the return-path is showing as user@whedoncon.com, but the DKIM is looking at hellmouth.org.</p>
  <p>So, TL:DR, google seems to always default to the signed-in account for the return-path, and not the secondary account that it's actually sending from.  Is there a way I can change the return-path so it matches the account the email is coming from, and not the account that I'm signed in as?</p>