| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Latest mutt can do this for MS and GMail providers, provide support for
getting the right scope and some examples how to set it up.
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The OAUTH credential server allows CMS to ack as an OAUTH broker and
supply bearer tokens to other applications in the system. Currently this
only support SMTP tokens for outbound mail delivery.
A UNIX domain socket is used to communicate between the SMTP agent and CMS.
A simple one line protocol is used to specify the account requested and
CMS returns the plain XAOUTH2 response string. The agent is responsible to
base64 encode it.
This works for GMail and O365 mailboxes.
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
| |
|
|
|
|
|
| |
Access to the headers like List-ID allows some client side filtering of
incoming messages.
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
| |
|
|
|
|
| |
For Gmail and other notes about O365
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
This allows treating the local message flags as authoritative during
program startup. Messages marked locally as deleted will be deleted on the
server during startup.
For safety, this never considers the absence of a message locally as a
deletion.
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
| |
|
|
| |
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
|
|
I have been using for a few months now with no ill effects.
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
|
