Jump to content
McKay Development

MailGuard spontaneous activation


Recommended Posts


Previously, my software had authorization of a newly registered account followed by saving authorization cookies via the following code:

const client = new (require('steam-user'))({
[`${[[PROXY_TYPE]].toLowerCase()}Proxy`]: [[PROXY_STRING]],

[[COOKIES]] = await(new Promise((resolve, reject) => {
    client.on('webSession', (_, cookies) => {

    client.on('error', reject);

        accountName: [[LOGIN_STEAM]],
        password: [[PASSWORD_STEAM]],

but after some time I noticed that after such authorization - Steam turns on MailGuard spontaneously (if at the same time to fill out the profile, through requests, then turning on MailGuard - 100%).

In the same order of actions, but through emulation (I do everything through BAS) - MailGuard is not spontaneously enabled

I am wondering if there is any way to fix this so that MailGuard is not turned off all the time?

Or, is it possible to do authorization via steam-session, since I get RefreshToken after registering an account?

Here's an example of Steam's response after registering:


Many thanks!

Edited by Dr. McKay
Removed PII refresh token
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...