From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-2.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 6B967202AA for ; Tue, 26 Feb 2019 17:54:48 +0000 (UTC) Received: by mail-wm1-x32a.google.com with SMTP id j125so3122245wmj.1 for ; Tue, 26 Feb 2019 09:54:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loskot-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=T8HgSdZDz3Zqa/SnRA7cqRAuifeny4q+3CJbWE7WDh8=; b=zateyO81K5e1e+xjVcBAcFwvv/Nm+pZ93YLg8hhP7MF6Wb/3pLD8g5dxJ/T+6FTxMN wNlfChtqYFf3/DRvbnu16v5v6gpOSRKqS2rvwUrlHJWqw5Mmtz2C8yqK2UZfSwoWHnY4 0NIbkbYH+F2ldR8BhPc/e4HWgaMxTf7QgsjByTyIlXwb7d5RRTECzKBn41t6hRo+LgQQ O9IetasohNWrNR/7paztD2fFwFrnz1ux19N0Fhwl30K1EmXNUE+wm7Vcq4NfXAQkfGEG nBZ79h/hqkyE3AFOqi4DDyofvozHnbc6yE6uJ2LMXPdLQ56g/CQY6Qx7wQXa+TM6SU0w jPTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=T8HgSdZDz3Zqa/SnRA7cqRAuifeny4q+3CJbWE7WDh8=; b=gMzahlslGH/WVf1ju/HpEmheVXYJpzvDYLBldCm9SmRJ9ohlOdOmuHQjPrnMsMKRYM +TneYR6TNppbHqIVYHYTnfooSRVDq9iunj8cIWIRLsU70n/Cig27hZaFDp+twJXGUNJE ZEo5NNKGWIZtzlMMlxYlN3hjjmHNK3URXDi75ADObf42SfKZN8BFHX+p6+vR2D+apvm8 LrXw65lg0anM5mRkrYAE/6MAojbe2dlAAjE6QVubM5ZZjr8Iu5t1a2zsAwXwEu55snBQ Y1YBymvo+sy0M7UTQZZraAJtAOsycC0FzjUUMZeusVCMGHAnBGTpp25mGdgmlL9fJYfT apIQ== X-Gm-Message-State: AHQUAub6N6b07N3R+81KNoUer5p1p9LJwozwr2C2nvq6zrldSDhfp9tJ +J3ONrPFCmRTXH9vMgYGsJMnEQ== X-Google-Smtp-Source: AHgI3IaRZLTGjhhrCOXkguLGHcnpxyKDK3fqsLO0HcNkS24QbjcpMge7e4/gu8OhFQlJaIBcLkf6Pw== X-Received: by 2002:a1c:ab88:: with SMTP id u130mr3413976wme.148.1551203683534; Tue, 26 Feb 2019 09:54:43 -0800 (PST) Received: from DEV604.cadcorp.net ([195.99.130.66]) by smtp.gmail.com with ESMTPSA id a1sm18212017wrq.96.2019.02.26.09.54.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 26 Feb 2019 09:54:42 -0800 (PST) Date: Tue, 26 Feb 2019 18:54:40 +0100 From: Mateusz =?utf-8?Q?=C5=81oskot?= To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Mirroring mailing lists directly Message-ID: <20190226175440.zni6w3fcmgz46gbm@DEV604.cadcorp.net> References: <20190223031048.GA7084@dcvr> <20190223220738.s5cij5pkqx7ke7ij@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190223220738.s5cij5pkqx7ke7ij@dcvr> User-Agent: NeoMutt/20171215 List-Id: On Sat, Feb 23, 2019 at 10:07:38PM +0000, Eric Wong wrote: >Mateusz Loskot wrote: >> [...] >> Is this plan correct, complete or am I missing anything? > >Looks close to me. Thank you for the confirmation and all the very useful tips. >I also suggest running public-inbox-nntpd in addition to -httpd >for NNTP users. It shares a common core with -nntpd and I have >plans for a combined server to minimize memory use. Yes, I will consider. Good idea. >> Do I need to bother with public-inbox-watch's bidirectional sync? > >There is no bidirectional sync in -watch. Perhaps you mean >offlineimap? Of course, it's offlineimap. >You may also want to prevent your Maildir and IMAP folder from >growing too large. You can setup a cronjob to remove old mails >from the Maildir; which causes offlineimap bidirectional sync to >remove the old messages from IMAP, too. > >The following example removes mails older than 7 days: > > cd /path/to/Maildir && > find new cur -ctime +7 -type f -print0 | xargs -0 rm -f Good idea. I have successfully married offlineimap and mutt a few days ago, for GMail, so I now have pretty good understanding of this workflow. >> Once I get to the 4. and later points of the plan above, >> I will get back to your other suggestions on the implementation >> details. > >Alright, please do :) I haven't done it yet. Meanwhile, if it's nota secret could you tell a bit about hosting of the public-inbox.org? Is this a VPS or a VM solution, a docker container? If a container, could you tell where do you host it? I'm still looking for options. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net