# mbsyncrc based on

# http://www.ict4g.net/adolfo/notes/2014/12/27/EmacsIMAP.html

# ACCOUNT INFORMATION

IMAPAccount gmail

# Address to connect to

Host imap.gmail.com

User <EMAIL_HERE>

PassCmd 'gpg2 -q --for-your-eyes-only --no-tty -d ~/.emacs.d/mu4e/.mbsyncpass-<EMAIL_HERE>.gpg'

AuthMechs LOGIN

SSLType IMAPS

SSLVersions TLSv1.3

CertificateFile /etc/ssl/certs/ca-certificates.crt

# THEN WE SPECIFY THE LOCAL AND REMOTE STORAGE

# - THE REMOTE STORAGE IS WHERE WE GET THE MAIL FROM (E.G., THE

# SPECIFICATION OF AN IMAP ACCOUNT)

# - THE LOCAL STORAGE IS WHERE WE STORE THE EMAIL ON OUR COMPUTER

# REMOTE STORAGE (USE THE IMAP ACCOUNT SPECIFIED ABOVE)

IMAPStore gmail-remote

Account gmail

# LOCAL STORAGE (CREATE DIRECTORIES with mkdir -p ~/Maildir/gmail)

MaildirStore gmail-local

Path ~/Maildir/gmail/

Inbox ~/Maildir/gmail/INBOX

# REQUIRED ONLY IF YOU WANT TO DOWNLOAD ALL SUBFOLDERS; SYNCING SLOWS DOWN

# SubFolders Verbatim

# CONNECTIONS SPECIFY LINKS BETWEEN REMOTE AND LOCAL FOLDERS

#

# CONNECTIONS ARE SPECIFIED USING PATTERNS, WHICH MATCH REMOTE MAIl

# FOLDERS. SOME COMMONLY USED PATTERS INCLUDE:

#

# 1 '*' TO MATCH EVERYTHING

# 2 '!DIR' TO EXCLUDE 'DIR'

# 3 'DIR' TO MATCH DIR

Channel gmail-inbox

Far :gmail-remote:

Near :gmail-local:

Patterns 'INBOX'

Create Both

Expunge Both

SyncState *

Channel gmail-sent

Far :gmail-remote:'[Gmail]/Sent Mail'

Near :gmail-local:'Sent Mail'

Create Both

Expunge Both

SyncState *

Channel gmail-all

Far :gmail-remote:'[Gmail]/All Mail'

Near :gmail-local:'All Mail'

Create Both

Expunge Both

SyncState *

Channel gmail-starred

Far :gmail-remote:'[Gmail]/Starred'

Near :gmail-local:'Starred'

Create Both

Expunge Both

SyncState *

Channel gmail-trash

Far :gmail-remote:'[Gmail]/Trash'

Near :gmail-local:'Trash'

Create Both

Expunge Both

SyncState *

# GROUPS PUT TOGETHER CHANNELS, SO THAT WE CAN INVOKE

# MBSYNC ON A GROUP TO SYNC ALL CHANNELS

#

# FOR INSTANCE: 'mbsync gmail' GETS MAIL FROM

# 'gmail-inbox', 'gmail-sent', and 'gmail-trash'

#

Group gmail

Channel gmail-inbox

Channel gmail-sent

Channel gmail-trash

Channel gmail-all

Channel gmail-starred

ProtonMail Account Creator 🚀 Create endless amounts of free ProtonMail Accounts. 🚀 🏗 Manage your free ProtonMail Accounts. 1.0.2 📌 🤖 Full Proxy Support 🤖 Features. Random inputs for Username & Password ️; Save Account details after Creation in.cvs file 🧾 Use CrawledProxies or use proxy file 🤫 Full Auto. Twitter account creator. GitHub Gist: instantly share code, notes, and snippets.

Change <EMAIL_HERE> to your actual Gmail username. Save your Gmail password at ~/.emacs.d/mu4e/.mbsyncpass-<EMAIL_HERE> Encrypt it with Delete the original plain password file for obvious security reasons.

Complete the steps described in the rest of this page to create a simple PHPcommand-line application that makes requests to the Gmail API.

Prerequisites

To run this quickstart, you need the following prerequisites:

• PHP 5.4 or greater with the command-line interface (CLI) and JSON extensioninstalled
• The Composer dependency management tool
• A Google account with Gmail enabled

Step 1: Turn on the Gmail API

Click this button to create a new Cloud Platform project and automaticallyenable the Gmail API:

In resulting dialog click DOWNLOAD CLIENT CONFIGURATION and save the filecredentials.json to your working directory.

Step 2: Install the Google Client Library

See the library's installationpage for the alternativeinstallation options.

Step 3: Set up the sample

Create a file named quickstart.php in your working directory and copy in thefollowing code:

Step 4: Run the sample

Run the sample using the following command:

The first time you run the sample, it will prompt you to authorize access:

1. Browse to the provided URL in your web browser.

   If you are not already logged into your Google account, you will beprompted to log in. If you are logged into multiple Google accounts, youwill be asked to select one account to use for the authorization.

2. Click the Accept button.
3. Copy the code you're given, paste it into the command-line prompt, and pressEnter.

Notes

• Authorization information is stored on the file system, so subsequentexecutions will not prompt for authorization.
• The authorization flow in this example is designed for a command-lineapplication. For information on how to perform authorization in a webapplication, seeUsing OAuth 2.0 for Web Server Applications.

Further reading

Troubleshooting

This section describes some common issues that you may encounter whileattempting to run this quickstart and suggests possible solutions.

SSL certificate problem: unable to get local issuer certificate

This error indicates that the underlying HTTP libraries can't find a certificatestore, and are therefore unable to setup the SSL connection to Google's servers.See the Guzzle library's documentationfor information on how to setup a certificate store on your machine.

Uncaught InvalidArgumentException: missing the required redirect URI

This error occurs when the credentials.json file used contains a clientID of the wrong type. This code requires an OAuth client ID of type Other,which will be created for you when using the button in Step 1. If creating yourown client ID please ensure you select the correct type.

This app isn't verified.

Gmail Creator Bot

The OAuth consent screen that is presented to the user may show the warning'This app isn't verified' if it is requesting scopes that provide access tosensitive user data. These applications must eventually go through theverification process toremove that warning and other limitations. During the development phase you cancontinue past this warning by clickingAdvanced > Go to {Project Name} (unsafe).