iCE40/yosys - clone of https://github.com/YosysHQ/yosys

diff options

Diffstat (limited to 'backends/verilog')

0 files changed, 0 insertions, 0 deletions

# Cloud MailDir Sync This program will download a mailbox from the cloud into a local maildir, monitor the local maildir for changes, then upload those changes back to the cloud. It is intended to allow normal Linux MailDir based progams, such as mutt and gnus, to work with modern cloud based email. There is much similarity to mbsync, but this program does not use IMAP for manipulating email on the server. ## Ideal Usage Although other use cases are possible, CMS was designed to support a 'Inbox Zero' kind of workflow where email is read on a Linux laptop/desktop. It supports multiple readers, including using the native cloud readers concurrently. Although it will function, it has not been optimized for giant email boxes and may not perform well. For safety it operates only in an 'online mode' where the daemon must be running. Any local changes made to the mailboxes when the daemon is stopped are discarded. A '--offline' flag will keep changes to flags in the local mailbox (but ignores removed maildir files). This is relatively safe but could potentially loose flag changes done on the cloud side. # Microsoft Office365 Cloud Mailbox The motivating reason to create this program was to support email from Office365 using modern OAUTH2 based authentication. Not only is the IMAP service in Offic365 very poor, it currently does not support OAUTH2 and is thus often blocked by IT departments. This often means there is no good way to access email from a Linux systems. CMS's Office365 interface uses the [Microsoft Graph REST](https://developer.microsoft.com/en-us/graph) interface over HTTP to access the mailbox. Internally this uses a multi-connection/multi-threaded approach that provides much better performance than the usual Office365 IMAP service. There is limited support for push notifications for new email as the Graph interface does not support any way for clients to get notifications. Instead an old OWA REST interface is used to get notifications. Unlike IMAP, CMS is able to set the 'replied' flag in a way that shows up with the other Outlook based clients. CMS is also able to set the 'ImmutableId' flag which causes the server to provide long term stable IDs for the same message. This avoids more cases where the messages have to be re-downloaded to again match them to local messages. # Gmail Cloud Mailbox While Gmail has fairly good IMAP support, and does support OAUTH2 to IMAP, the REST interface is a bit more scalable and robust. CMS uses the [Gmail API](https://developers.google.com/gmail/api/guides) to access the mailbox. It can be pointed at any Label in GMail and uses this history scheme to optimize updates. There is no support for push notifications as the Gmail API only considers


context:
space:
mode: