node cli.js method socket socket.path izy-pop3/proxypkg:directdb socket.testmod izy-pop3/proxypkg/test/android socket.verbose.writes true socket.verbose.ondata true socket.user user socket.pass password
If you need to debug the deployment over SSL without izy-proxy, use ncat --ssl. i.e.
`
`
`
USER user
PASS passLIST
RETR 1`
* modify state schema to contain more config options
* all the debugging, instrumentation mixed mode testing capabilities available in izy-proxy can now be used
* izy-pop3/proxypkg:directdb/mim modules have been implemented as a socket plug-in for izy-proxyparameters: //chain/izy-pop3/proxypkg:test/base
state: {"ip"server","port"995","user"
user@domain","pass"password","tls":true}
* Since .eml files are serialized octets from a RFC822 encoded message, the approach shown above would work perfectly fine and should generate interoperable stores that would work with standard compliant tools from 3rd party vendors.
* Also note that some providers (i.e. Gmail) would not allow authentication:
* If you use Multifactor Authentication, try signing in with an App Password (https://support.google.com/accounts/answer/185833), you might get the following error:
`
-ERR [AUTH] Username and password not accepted.
`
* Note that to setup an app password you will have to re-enter your password and get MFA code to your device.
* As an alternative you may just disable MFA for a short period of time while doing backups. Doing this will have GMail send a confirmation email:`
Review your recently used devices now.
`
* Notice that no confirmation is sent to your MFA device when this gets turned off.
* If you don't use Multifactor Authentication, you might need to allow less secure apps to access your account.* You might get the following error
`
-ERR [AUTH] Web login required: https://support.google.com/mail/answer/78754
`
and a follow up email gets sent:
`
Hi xxx,
Google just blocked someone from signing into your Google Account xxx@gmail.com from an app that may put your account at risk. Less secure appxxxx
Don't recognize this activity?If you didn't recently receive an error while trying to access a Google service, like Gmail, from a non-Google application, someone may have your password.
SECURE YOUR ACCOUNT
Are you the one who tried signing in?
Google will continue to block sign-in attempts from the app you're using because it has known security problems or is out of date. You can continue to use this app by allowing access to less secure apps, but this may leave your account vulnerable.`
* You should go to https://myaccount.google.com/lesssecureapps and allow access for this to work.
* When you turn that on, you will also get an email:`
Access for less secure apps has been turned on
`
`
`
Secureserver.net however, will respond by:
`
`
The general rule is that all responses from the server will start with one of the following:
`
-ERR
`
`
node cli.js method test testtype mimestore mimestore.modhandler fake query.limit 2 query.tags abc
node cli.js method test testtype mimestore mimestore.modhandler cloud mimestore.accesstoken xxxx mimestore.dataservice https://yourcloudlocation mimestore.verbose true mimestore.tablename yyy.xxx query.limit 2 query.tags abc`
`
node cli.js method serverpop3 port 1110 password 12345 mimestore.modhandler fake
node cli.js method serverpop3 port 1110 password 12345 mimestore.modhandler cloud mimestore.dataservice xxx mimestore.xxxssh -i identity.pem -4 -v -R 1110:localhost:1110 user@your-server.com
node cli.js method clientpop3 ip pop.secureserver.net port 995 user user@domain pass 'password' tls true verbose.clientLog cmd listnode cli.js method clientpop3 ip pop.secureserver.net port 995 user user@domain pass 'password' tls true mimestore.modhandler localfs mimestore.path /tmp/izyware/mimestore cmd retr query 1-10
`