Re: Mulberry-discuss Digest, Vol 100, Issue 2
Christer Mjellem Strand <[email protected]> Tue, 04 Apr 2023 16:22:37 +0200
| Newsgroups | gmane.mail.mulberry.user |
|---|---|
| Message-ID | <1801AB499D46AA01E16A12CC@plopp> |
--==========8048F9D71C88CFBCB3C5========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; size=1530 [..] > I think I understand about a web-based client accessing > web-based servers, but does keeping the present setup require > that I run a web server more or less co-located with the mail > one(s)? If so, does the configuration to handle both local IMAP > servers and remote ones happen there? [..] This is the way things commonly tend to be set up, but it is by no=20 means a requirement. A web server (with Roundcube) can run anywhere,=20 and as long as it's able to reach the IMAP server, that too can run=20 anywhere. You wanna be sure that the communication between the two is=20 sufficiently encrypted and protected (equally true for any client=20 accessing your IMAP server[1], of course), but in principle, webmail=20 such as Roundcube really is just another client - one you open in a=20 browser rather than as a local separate application. [1] In the case of webmail you also want to ensure communication=20 between your browser and your webserver is equally protected, as that=20 becomes another layer of client/server relationship. You can run it=20 locally on your own computer, which negates most risk, but then it can=20 only be accessed from there. If you want to expose it to the Internet,=20 you can use Let's Encrypt with a client like certbot to get a free=20 (valid) certificate, and Mozilla's SSL Configuration Generator to=20 ensure sane crypto parameters: <https://ssl-config.mozilla.org>. The latter works for Dovecot too, should that happen to be your IMAP=20 server of choice. --=20 Christer Mjellem Strand System Administrator --==========8048F9D71C88CFBCB3C5========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQFHBAEBCgAxFiEEFhmg5QS3gto1QlUc+lb3xtijdwEFAmQsMq0THGRpbGxkYWxs QGJqb3JrLm9yZwAKCRD6VvfG2KN3AboQCACrrMVBfOhY8ZZdBk+0B3IezS/rRjlO lBpQq8hE71+DtYTNU6FNN8z48RaKDSlVDiWoSvZL1FsYszowq2y7wENLyj7PNkke TBP9Aso56+UQgx0kNJbx79Eoqbb4U0fVl5uU5WRBNA+JkctKCIUYDd+OWMF6ve/l 0HHy6BP2WTypKmDcFITAWPP7/1zh5uSWuxi4XAyowFhlcycB8TgcX0AfSfL9pnZ8 4neJVGJ/znnaXS/jUYgaV1zlLRdjY8QX6Lxay3c12C4xbOepTey+bhicI4y6T5TC dIjlEk3I2Csc9yyh4xGgsbaD1WgoRNvHRoowcsh3oH9DF6pdYc4orT6k =EA9W -----END PGP SIGNATURE----- --==========8048F9D71C88CFBCB3C5==========--