Re: maildir - whats the skinny?

[Harry Putnam <reader@newsguy.com>]

"Matt Armstrong" <matt@lickey.com> writes:

[...]

>> Each beginning with what `formail' thinks are more message headers.
>
> Slightly off topic, but formail has an -m argument.  By default
> formail will think it sees a new message when it sees 2 headers in a
> row.  Use -m 5 and it'll require 5 headers, which might fix the
> problem.

Haa... yeah that is exaclty what I am seeing.  Messages created on the
strength of 2 header like lines.  Seems like formail would pay more
attention to the dot on a line by itself and only print when that has
shown up.  Probably introduces other problems or sloth.

[...]

> I run "leafnode" (http://www.leafnode.org) to have a local nntp cache
> of the groups I read.  Accessing the messages is still slower than an
> nntp group, but fast enough for me.  Leafnode allows you to post to
> it, and then it goes and posts to the main server when you tell it to.
> So even if you don't read news via leafnode, you can post to leafnode
> as a kind of nntp send queue.  (there may be a better way though)

I ran that for a little while once but it doesn't really change any
thing inside gnus.  The news is still in the restricted category of
nntp. And leafnode trys to be a little too smart for its own good with
the heuristics.  I thought that the agent categories and activate
levels etc gave more functionality.  So went back to regular nntp
server. 

I tried slrnpull for a while too.  I think it is better than leafnode
in that it doesn't outsmart the user so much.  But again there is no
gain inside gnus.  But converting news to mail on the other hand,
opens up quite a lot more fucntionality.