MailNews

Nemo's notes on making mutt work for newsgroups, via some helper utilities that talk nntp, and scripts which bind them together.

Reading

slrnpull pulls messages into it's own spool. This spool is readable with mutt directly (it seems to treat it as an 'mh' format mailbox.

However, this means that the messages default to being marked as 'read', and unless you control your own spool, you can't even change that!

news2Maildir

news2Maildir is basically an extremely simple news client (not even an nntp client, since it only looks at the local news spool), and ALSO acts as a MDA to a very select number of Maildirs.

It will operate by copying each message from the spool and deliver it to a Maildir folder. Thus messages appear as new and unread to mutt, and can be read, flagged, deleted, as expected.

news2Maildir will need to keep track, per group, as to which message it saw last. Maildir folders should be named exactly as the group is named.

It should operate in a read-only fashion on the spool, though if you operate your own spool, it could have the option to clear it for you. (imho, better to let slrn do it's own job there)

news2Maildir should only fill the Maildir's that are in existance. However, if you operate slrnpull as a user, then perhaps it could update slrnpull.conf appropriately if newsgroup Maildir's are created/deleted.

I propose these newsgroup based Maildirs live within ~/Newsdir

Writing

Minimum post requirement for slrnpull

A post in the var/spool/slrnpull/out.going/ directory needs to be only named "X", and can get away with only From:, Newsgroups: and Subject: headers, along with a body. Upstream servers will fill out the remainder.

The file needs to be protocol encoded - that is, any lines with a leading "." needs that . to be doubled.

For eg, a file with these contents

From: Nobody <devnull@home>
Newsgroups: alt.test
Subject: test 2

test
.testone
..testtwo
...testthree

---

• See also Maildir on this wiki