FastMail Sync Issues

[cooperpellaton]

I configured N1 with my main account: one from FastMail to which all of my domains are attached. All of my folders were successfully synced but no emails were. Using the search field, which I assume queries the server, also returns nothing. I'm at a loss. This combined with the fact that once the account details are put in they do not appear to be changeable leave me not understanding why the emails won't sync.

Could it be an issue at the TLD level where all of my emails from my domains that forward to my FastMail address are not being seen through the FastMail IMAP, or JMAP, implementation?

No emails loaded throughout the entire application:

Lack of ability to change account details after setup:

If you can change the above, then that UI paradigm is extremely flawed because I clicked in many places and scoured the settings to find nothing.

[mbilker]

Does FastMail use IMAP?

What is inside ~/Library/Application Support/Nylas N1/config.cson? You should be able to tweak some parameters in there. The lack of customization is due to the separation of the sync engine and the client.

[cooperpellaton]

FastMail is using a flavor of IMAP that is cleaned up JMAP and they are moving to full JMAP soon. I went to look for that config file to find nothing. This is the directory listing of that address.

To note, the emails in the inbox did eventually load, as did the labels for my folders, but none of the contents of the folders every sync'd which makes no sense as IMAP/JMAP should permit that.

[mbilker]

ok. It's actually ~/.nylas/config.cson and beware it has personal information pertaining to account authentication with the sync engine server.

[cooperpellaton]

I've removed a lot of the private information so I can post the file below. As far as I can tell nothing looks out of the ordinary. I'll take a look at the sync engine tomorrow and try and see if it has something to do with the way the folder contents is being parsed/dataset being handled separately from that of the inbox.

"*":
  core:
    disabledPackages: [
      "calendar-bar"
    ]
    workspace:
      mode: "split"
      hiddenLocations:
        MessageListSidebar:
          id: "MessageListSidebar"
          Toolbar:
            id: "MessageListSidebar:Toolbar"
  updateLevel: "patch"
  env: "production"
  updateIdentity: "d0522bc6-3e49-4cf2-a519-ac7f7e497f26"
  invitationCode: "c7332caed3224c69a08801e6d8326b88"
  nylas:
    accounts: [
      {
        client_id: removed
        server_id: removed
        object: "account"
        account_id: removed
        name: "Cooper Pellaton"
        provider: "custom"
        email_address: removed
        organization_unit: "folder"
        id: removed
      }
      {
        client_id: removed
        server_id: removed
        object: "account"
        account_id: removed
        name: "Cooper Pellaton"
        provider: "gmail"
        email_address: removed
        organization_unit: "label"
        id: removed
      }
      {
        client_id: removed
        server_id: removed
        object: "account"
        account_id: removed
        name: "Cooper Pellaton"
        provider: "gmail"
        email_address: removed
        organization_unit: "label"
        id: removed
      }
      {
        client_id: removed
        server_id: removed
        object: "account"
        account_id: removed
        name: "Cooper Pellaton"
        provider: "gmail"
        email_address: removed
        organization_unit: "label"
        id:
      }
    ]
    currentAccountIndex: 0
    accountTokens:
      removed
    mailto:
      "prompted-about-default": true
    removed:
      cursor: removed
    removed:
      cursor: removed
    removed:
      cursor: removed

[mbilker]

Remove the last three keys. They correspond to server/account_id, though they cannot be used without the accountTokens.

[cooperpellaton]

@mbilker Corrected. Although I initially left them in for the reason you mention, they correspond to the server and account_ids so without them they are worthless.

[mbilker]

This appears to be just inconsistency between FastMail and the Nylas Sync Engine. I may have to get an account to test this theory further.

[cooperpellaton]

@mbilker If you want to continue and post updates on this issue I'm more than willing to help as I have some knowledge of the FastMail JMAP spec.

[mbilker]

@cooperpellaton I suggest you also create an issue at the https://github.com/nylas/sync-engine repository so they are aware of this issue there where it is has the most significance. There are also many more issues listed at this repository dealing with client-side issues.

Well its 12:43am where I live. I am going to bed.

[moollaza]

FWIW I'm a Fastmail user and have had no problems with Nylas. All my folders are there and things seem to be working correctly.

I only have my Fastmail account connected to Nylas, and my account object in the CSON looks identical to yours.

Happy to help compare things if needed.

[grinich]

@cooperpellaton can you elaborate on this?

Could it be an issue at the TLD level where all of my emails from my domains that forward to my FastMail address are not being seen through the FastMail IMAP, or JMAP, implementation?

This indeed looks like a minor config issue with the sync engine that is causing a failure for your account. We've had a couple of reports here, and are looking into it.

[cooperpellaton]

@grinich FastMail is not hosting my DNS but I have 2 domains pointing there. I have auto routing enabled and have allowed FastMail to catch all email hitting them at the top level. I was considering that this might be handling in some specific way via the JMAP spec (though I would need to check) that they are not processing out bound via IMAP.

[grinich]

Thanks @cooperpellaton -- I'm going to close this issue on N1. Let's discuss at https://github.com/nylas/sync-engine/issues/225