user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC] ssoma-mda: Use the email subject as the commit message
Date: Mon, 20 Oct 2014 08:36:24 -0700	[thread overview]
Message-ID: <20141020153624.GS17200@odin.tremily.us> (raw)
In-Reply-To: <20141020004908.GA23299@dcvr.yhbt.net>

[-- Attachment #1: Type: text/plain, Size: 2946 bytes --]

On Mon, Oct 20, 2014 at 12:49:08AM +0000, Eric Wong wrote:
> W. Trevor King wrote:
> > On Sun, Oct 19, 2014 at 05:30:29AM +0000, Eric Wong wrote:
> > > W. Trevor King wrote:
> > > > On Sat, Oct 18, 2014 at 11:43:23PM +0000, Eric Wong wrote:
> > > > > Sounds like a good idea to make it fall back if require fails.  Can
> > > > > you do it or would you like me to handle it in Perl?
> > > > 
> > > > If you tell me the Perl idiom for that, I can write up a patch.  In
> > > 
> > > 	eval { require Foo; };
> > > 	my $have_foo = $@ ? 0 : 1;
> > > 
> > > That won't perform any imports, but I think most of those modules do
> > > not require imports.
> > 
> > And then if have_foo, we ‘use Foo’ to get the import?
> 
> No need to import for the Email::* modules I don't think.  "use" is
> evaluated at compile/parse time, so you can't use it lazily outside of a
> string eval.  "require" is always lazy, I think.
> 
> I think you can just call "IPC::Run::run" directly (instead of just "run")

Sounds good, I'll give this a shot for v2.

> > > > > public-inbox also wraps spam filtering/learning
> > > > > (SpamAssassin) + sanitization, and that's arguably more
> > > > > important than the web UI.
> > > > 
> > > > Then I'd shift those hooks over to ssoma-mda.  Actually, I'd
> > > > probably leave it up to folks to hook those into their mail
> > > > server / MDA before messages get as far as ssoma-mda.  Spam
> > > > filtering is a generic issue; there's no need to build all the
> > > > checks you'd want (also greylisting, DKIM, SPF, …) into
> > > > ssoma-mda itself.
> > > 
> > > Uh, you just contradicted yourself :) public-inbox is that mail
> > > server/MDA layer before ssoma for me.
> > 
> > Filtering spam is something that lots of folks want (folks who may
> > not be interested in Git archives), and it should happen at the
> > MTA level (e.g. [1]) or in a procmail chain (e.g. [2]).  The spamc
> > hook shouldn't be tied to any Git-archive stuff.  I'd shift the
> > Git metadata extraction to ssoma-mda, use the Postfix filtering to
> > drop spam for everyone, use procmail to deliver mail for everyone,
> > and then call ssoma-mda from ~meta/.procmailrc.
> 
> I don't disagree with the metadata extraction for ssoma-mda; but
> everything above that layer (including public-inbox) should be open
> to interpretation.  I don't use procmail myself, for example; and I
> know folks who would want to use extra/different spam filters.
> 
> public-inbox is my opinionated policy layer; but ssoma was intended
> to be generic.

Fair enough.  Maybe I'm looking for a generic ssoma-archive-to-HTTP
server (like public-inbox.cgi) that is independent of the opinionated
filtering in public-inbox-mda?

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy


  reply	other threads:[~2014-10-20 15:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 20:19 [RFC] ssoma-mda: Use the email subject as the commit message W. Trevor King
2014-10-18 21:04 ` Eric Wong
2014-10-18 21:50   ` W. Trevor King
2014-10-18 23:43     ` Eric Wong
2014-10-19  3:48       ` W. Trevor King
2014-10-19  5:30         ` Eric Wong
2014-10-19 17:31           ` W. Trevor King
2014-10-20  0:49             ` Eric Wong
2014-10-20 15:36               ` W. Trevor King [this message]
2014-10-20 19:26                 ` Eric Wong
2014-10-20 19:53                   ` W. Trevor King
2014-10-26 22:57         ` Eric Wong
2014-10-27  0:19           ` W. Trevor King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141020153624.GS17200@odin.tremily.us \
    --to=wking@tremily.us \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).