From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] 9 Atom - installation troubles
Date: Sat, 6 Dec 2014 06:57:28 +0200 [thread overview]
Message-ID: <a603058714c460f0e7809e897765ea8b@proxima.alt.za> (raw)
In-Reply-To: <20141205222130.4EAF6B827@mail.bitblocks.com>
> It is what it is. Not worth spending your time learning the
> details of email related RFCs and how they are used & misused.
> Instead write a nice useful 9p filesystem!
I could not agree more. But I've caught up with RFC 5322 recently: my
current project (I am getting paid a nominal amount to indulge in it)
involves using multiple SPAM reports to name and shame spammers
operating in contravention of South African legislation. Go provides
an amnazing platform to develop in and I have developed my share of
tools to analyse email messages for this. After my first serious
refactoring (I'm learning, but at my age it takes a bit longer) I'll
be happy to release the code. Anybody who wants to look at it now can
do so, but will need to suffer the indignities of CVS without
anonymous access (just ask me for a login account - it's on a NetBSD
server).
I'm writing this in knee-jerk reaction to your suggestion, so let me
first thank you for taking the trouble. I'd be very happy to
reconstruct upas (and Erik's nupas, which I have ignored against my
better judgement) as a Go application to do things more sensibly, but
I think I'd firsl like to poll the community for ideas.
If I discover anything interesting by inpecting the mkessage headers
(thanks, once again), I will report about it here.
Lucio.
-------------------------------------------------------------------------------------
This email has been scanned by the MxScan Email Security System.
-------------------------------------------------------------------------------------
next prev parent reply other threads:[~2014-12-06 4:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 10:02 lucio
2014-12-05 14:20 ` erik quanstrom
2014-12-05 17:47 ` lucio
2014-12-06 19:02 ` erik quanstrom
2014-12-07 4:26 ` lucio
2014-12-07 5:15 ` lucio
2014-12-07 7:26 ` erik quanstrom
2014-12-07 7:33 ` erik quanstrom
2014-12-05 18:04 ` lucio
2014-12-05 18:15 ` lucio
2014-12-05 20:38 ` Wes Kussmaul
2014-12-05 21:23 ` Skip Tavakkolian
2014-12-06 4:43 ` lucio
2014-12-05 22:21 ` Bakul Shah
2014-12-06 4:57 ` lucio [this message]
2014-12-06 16:34 ` erik quanstrom
2014-12-06 18:12 ` lucio
2014-12-06 18:53 ` erik quanstrom
2014-12-06 5:06 ` lucio
2014-12-06 9:09 ` lucio
2014-12-06 9:27 ` Bakul Shah
2014-12-06 10:28 ` Quintile
2014-12-06 13:40 ` lucio
2014-12-06 16:29 ` erik quanstrom
2014-12-06 16:42 ` Kurt H Maier
2014-12-06 17:47 ` lucio
2014-12-06 13:43 ` lucio
2014-12-06 14:06 ` lucio
2014-12-06 14:30 ` lucio
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a603058714c460f0e7809e897765ea8b@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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.
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 NNTP newsgroup(s).