|
On 2016-09-14 02:34, Paul Lesniewski
wrote:
Thank you for your answer.Sorry for the delay. Please post this kind of message to public mailing lists, not to personal email addresses. No problem except for having to subscribe to and drown under dozens of lists. Thanks for letting me know that it would need modifications to SquirrelMail IMAP Proxy to support Read Only public access.Please forward to possible more appropriate recipients.I have subscribed to several mailman lists, e.g. tagging tagg...@openstreetmap.org <https://lists.openstreetmap.org/listinfo/tagging>. I used the same gmail account as subscriber for all of them. I direct each list's e-mail into its own folder (gmail "label") with a gmail filter. Accessing that archive to search it, reply to old messages etc. is a real convenience. I'd love to share that archive with other people. But giving them write access to it would mean its deterioration. Si, I wondered if Imapproxy is able to provide public, read-only access to such a server.SquirrelMail IMAP Proxy could be changed to block a list of IMAP commands, but it would be better if you created a list of commands that were acceptable and block all others. Still, keep in mind that even "innocent" commands such as that to read a message can make changes in the message store (in this case, potentially change a message state from unread to read). It's possible there could be worse examples. But, if someone wants to come up with a list of IMAP commands that would comprise a read-only proxy setup, I'd consider adding it since it looks somewhat trivial (FYI, ~line 1354 in Raw_Proxy() in src/request.c). I'm not sure, however, if there would be other ill effects (for example, responding "NO" or "BAD" to disallowed commands might confuse the client, as would issuing a faked (dishonest) "OK" response).And if someone could make the configuration and provide a server to run that experiment?BTW, you'd want to configure auth_sasl_plain_username, auth_sasl_plain_password and auth_shared_secret and give out the shared secret to anyone allowed to use the system. Have fun proxying mass access to Gmail - feels like any number of things could go wrong. I browsed gmain.org for an explanation of how it works and all I could find is "Any public mailing list can be carried by Gmane". When I tried to open the mailing lists links IO found, all I got is "problem loading page".I would extend the configuration and make the mailman to gmail message conversion. I run a few byethost-like free servers. I don't know if that imapproxy configuration could be installed on them. If that were possible, I would do it.My gut says there are better ways to provide mailing list archives to the public. Maybe you should collaborate to bring back gmane.org (oh wait, it's back). The system I use and suggest in public R/O mode is ideal because all it needs is a plain IMAP MUA and server. You get the full search and reply etc. capabilities that you have with your own IMAP folders. Unfortunately, mailman's Mark Sapiro is not convinced Unfortunately too, many people have fallen in the trap of using Webmails whose first shortcoming of many is to be unable to use several IMAP servers (and hence to copy e-mail to a backup server. Webmails and the way people use IMAP have made e-mail a bad reputation). So, my best option is to continue to enjoy that system for myself. But if you came up with a R/O public version and if I had simple instructions and a server to run it, I would certainly set up demo versions of it, including converting old e-mail logs to IMAP. Thanks for your attention. Cheers
|
------------------------------------------------------------------------------
----- squirrelmail-imapproxy mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-imapproxy@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy
