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-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id C36101F9FD for ; Fri, 26 Feb 2021 19:29:56 +0000 (UTC) Received: by mail-qv1-xf2e.google.com with SMTP id n4so2720028qvl.4 for ; Fri, 26 Feb 2021 11:29:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Ur9+e5jfoWrtBPO3H/8+muddF8Hg2XyR0p02eB/Sifk=; b=H9o70lHGOqMrVfGA28B2FIcNiION9GclpeKuZjU7VDtLM0iFBzlY2OGG32i8r9No6f WxDHiiAmss4DfEGjC5a3Jc+yid4VVCIpbwbmDhwXraoJdmQg1cOusnw6jx9iG2oB1vp1 KQWedxgb+kLQB8s+P+g8isEUMldiJPh8BNHrc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Ur9+e5jfoWrtBPO3H/8+muddF8Hg2XyR0p02eB/Sifk=; b=YECMCj6gW9pfp58T+nLY6HusIfR9vKAxShtE/lHHZcfEppnD1KiBvNbb8XTTW+399G VRIHdh6iAP03sU6h0YPjxC8JncbVvQ/2HGWKShFxQ/HdyOsf9iTAHZdf6SCOYcS/tZUa qr9i6hwjkfEBFgkxr7I4ZvKdFQwoLC1Y/khSjOn3di9l0bapK+SdHQf7QsDgD2JFyd7v Y9PmzVr4P1RQ6DvWu+1jObhYBWYDHDhA5bv9BAH4aAyuTAl7iPM0C2yMWJ9uWmD6mqxK IA4RffYZUShVlgws/t/yw1V+1VhR43RCvA/lqoCjKryDCn3xVaqTnQMRTtShsVhq+rY4 +2Rw== X-Gm-Message-State: AOAM530B0n8GgIb/JYOvrX0eT5Mom4srgenPW7adLAf20IwEoEUOcu2s vQ69vfRihMkkotcnOc0t+23aWcvjJu+hQlyb7/hLOyaLDpnb+Q== X-Google-Smtp-Source: ABdhPJz/iwjkJQl9xK9ej5TXjY6p3yv0RfKxirqgr2YEUvBurKEemH/1mdvMWF1EkDrziZ4AGd3z6GNJxrt8Ya/bClY= X-Received: by 2002:a05:6214:1424:: with SMTP id o4mr4392882qvx.34.1614367794603; Fri, 26 Feb 2021 11:29:54 -0800 (PST) MIME-Version: 1.0 References: <20210226143806.6hu2775yroqaqynj@chatter.i7.local> In-Reply-To: <20210226143806.6hu2775yroqaqynj@chatter.i7.local> From: Konstantin Ryabitsev Date: Fri, 26 Feb 2021 14:29:43 -0500 Message-ID: Subject: Re: watch a simple dir To: meta@public-inbox.org Content-Type: text/plain; charset="UTF-8" List-Id: On Fri, 26 Feb 2021 at 09:38, Konstantin Ryabitsev wrote: > - it's a simple flat dir of numeric files corresponding to the number of the > message in the index > - each message is a valid rfc2822 document -- in fact, if I copy them into the > "new" folder of any maildir, I can read them with mutt > - however, if I use symlink trickery to make mlmmj deliver into "new" or "cur" > of a maildir monitored by public-inbox-watch, they are ignored -- so things > are not as easy as that. :) Probably, it expects to have more complex > filenames instead of just a number, but I didn't dig too deep. Ah, looks like this was only a limitation of v1.6.1 -- master doesn't require that filenames in new/ contain a :2 (which is not a requirement for maildir files in "new/" -- they merely need to be unique; the :2, part is required for cur/ entries for adding flags). So, this will work out just fine as long as this behaviour doesn't go back to what is in 1.6.1 (which it shouldn't). Simply symlinking /var/spool/mlmmj//archive to /new is sufficient to automatically add mlmmj messages to the public-inbox archive and, as an added bonus, this will properly respect control/noarchive settings. Me pleased. -K