bind message gateway id

[rrrooommmaaa]

This PR binds message gateway id for pwd-encrypted messages

close#4269

---

Tests(delete all except exactly one):

• Tests added or updated

---

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

• addresses the issue it closes (if any)
• code is readable and understandable
• is accompanied with tests, or tests are not needed
• is free of vulnerabilities
• is documented clearly and usefully, or doesn't need documentation

[rrrooommmaaa]

Sorry for lack of info. Indeed, I suppose we didn't update FES yet. I'll let you know once updated.

Originally posted by @tomholub in #4284 (comment)

Should I keep this PR draft meanwhile?

[tomholub]

yup 👍

[tomholub]

Actually, the whole time we had FES 2022-05 running, which is the latest version.

Have you tried this smaller PR against a live instance, is it giving you any trouble?

[tomholub]

If you test it against a live instance and it works as intended, you can mark it as ready for review. Thanks! 👍

[tomholub]

Looks good - see comment below

[tomholub]

I think we can await this, and put it just after draftDelete. I suppose we could make the two calls in parallel if we want to speed it up a little bit.

[rrrooommmaaa]

Actually, the whole time we had FES 2022-05 running, which is the latest version.

Have you tried this smaller PR against a live instance, is it giving you any trouble?

I tried that in early February. I don't quite get it -- should I log in as @flowcrypt.com to connect to the right instance?

[tomholub]

I tried that in early February.

ok - that was likely on older instance

I don't quite get it -- should I log in as @flowcrypt.com to connect to the right instance?

correct - https://fes.flowcrypt.com will be used on @flowcrypt.com account. fes.example.com will be used on example.com account if it's running there, etc.