Disclaimer: This comment was automatically generated with AI. It can give some useful hints as to where to look for, but sometimes it can also give very inaccurate answers so takes this with a pinch of salt :).

To resolve the issue, follow these steps:

1. Retrieve Email Aliases: Modify the EmailService to include a method that uses users.settings.sendAs.list to retrieve email aliases.

async function getEmailAliases(userId) {
  const res = await gmail.users.settings.sendAs.list({ userId });
  return res.data.sendAs.map(alias => alias.sendAsEmail);
}

2. Associate Messages with WorkspaceMember: Update the message processing logic to check if the sender or recipient email matches any of the retrieved aliases and associate the message with the corresponding workspaceMember.

async function processMessage(message) {
  const aliases = await getEmailAliases(message.userId);
  const isAlias = email => aliases.includes(email);

  if (isAlias(message.sender) || message.recipients.some(isAlias)) {
    // Associate with workspaceMember
    associateWithWorkspaceMember(message);
  }
}

3. Create Contacts: Ensure that contacts are created for emails sent or received by these aliases within the ContactService.

function createContactIfNotExists(email) {
  if (!contactExists(email)) {
    createContact(email);
  }
}

function processMessage(message) {
  const aliases = await getEmailAliases(message.userId);
  const isAlias = email => aliases.includes(email);

  if (isAlias(message.sender) || message.recipients.some(isAlias)) {
    // Associate with workspaceMember
    associateWithWorkspaceMember(message);
    // Create contacts
    message.recipients.forEach(createContactIfNotExists);
  }
}

Update the relevant files in the services directory to include these changes.

References

We should store all aliases within our DB. If we try to hack this we will probably have more issues down the line

Not sure how we will keep this data fresh, is there a webhook update for alias creation/deletion?

@FelixMalfait We can try to implement alias webhook update once we have implemented it for messaging.

In the meantime, we could just fetch user aliases before at the start of the message import job (doing it at the same time as we refresh connectedAccount access token for example).

I would create an handleAliases ARRAY field to the messageChannel

@charlesBochet Great! As long as we store all alias and not just the first one perfect