| layout |
|---|
guide |
It goes without saying that emails are highly sensitive. A Switchboard application is only as secure as the server which it is on. Beyond personal use, great care should be taken to ensure that both Switchboard and its environment are secure.
When deploying Switchboard, you must understand the differences between the worker and client interfaces. Unless you have a good reason otherwise, the worker interface should never be publicly exposed.
To have control over what interfaces are exposed, it is recommended
that Switchboard's client port, 8080 by default, is closed to
external connections. Individual interfaces can be exposed using an
HTTP server's
rewrite
rules.
If you are unable to loin to a Gmail account using PLAIN
authorization it could be because of Google's fraud
detection. Usually, the flagged login must be from a different
geographic location, a remote server, or a proxy. The error should
provide a URL where you can confirm that you initiated the login
attempt.
{::comment} TODO - include shell {:/comment}
You also won't be able to login using PLAIN authorization if you are using Google's 2-step verification without an application-specific password.
For each account, one IMAP connection is created for sending commands, plus one IMAP connection for each mailbox to be monitored. This separation of responsibilites across IMAP connections allows for simpler management of the IMAP connections, though at the cost of using multiple IMAP connections.
While the Switchboard API provides some IMAP+IDLE like functionality, it is specifically intended to take the pain out of real time email processing across many users. IMAP is a sharp, if sometimes low-level and difficult, tool and will remain preferable for general purpose email tasks.