+5 for a new release.
Ken Hornstein wrote:
>> No, that's not true. We could decode on inc(1) to UTF-8. Every other
>> MUA (effectively) does that these days.
> Sigh. That doesn't help with image/jpeg, video/mpeg, application/pdf
> ... all of those things which are not text. T
Ken Hornstein wrote:
> them) to Maildir filenames. That seems solvable somehow. But the main
> gain of Maildir seems to be lack of locking requirements ... am I
> missing something? Is it more about interoperability with other
> software?
It's mostly about interoperability to
Lyndon Nerenberg wrote:
>> message numbers are, indeed, "the problem." when i asked mark crispen
>> why IMAP was so hostile to the message numbering concepts of MH, he
>> muttered something about MM.
> But he did buy into, and accept, the UID concept. We had that
> conversat
Everyone,
I'd like to focus in this email JUST on the idea of a new release. I'll
send another email regarding future directions so we can keep these
discussion separate.
So, in short: cut a 1.7, yes or no? Anything people would like in there?
My list is:
- Incorporate XOAUTH support
- Fix cha
On Tuesday, March 8, 2016 9:19:57 PM PST Ken Hornstein wrote:
> ... I hate
> to be the the one who has to explain this ... that hasn't been a realistic
> goal since the advent of MIME. The model that "email is text" just
> isn't valid anymore.
i know. which is why i don't see much value in the mh
On 9 March 2016 at 9:17, Ken Hornstein wrote:
> So, in short: cut a 1.7, yes or no? Anything people would like in there?
> My list is:
>
> - Incorporate XOAUTH support
> - Fix character conversion on message bodies (right now it aborts if it
> cannot convert characters to the target characte
So, since my simple question about a new release spawned a whole thread
about the future direction of nmh I wanted to create a distinct thread
to discuess those ideas. If you're interested in commenting on future
ideas for nmh, this is the place to do it.
I am first going on the assumption that c
Ken Hornstein writes:
>
>4) In terms of alternate mail stores, be they Maildir or IMAP (I think
>those are the two major candidates now, right?), I think those ideas
>are interesting. The #1 problem with those ideas is how to map MH
>message numbers (which can range 1-MAXINT, with holes) to the
>>4) In terms of alternate mail stores, be they Maildir or IMAP (I think
>>those are the two major candidates now, right?), I think those ideas
>>are interesting. The #1 problem with those ideas is how to map MH
>>message numbers (which can range 1-MAXINT, with holes) to the internal
>>key used by
Ken> I am saying that we have people who want to use the nmh tools with both
Ken> IMAP and Maildir mailstores. So making the nmh tools work with those
Ken> mailstores would be useful.
.. with migration via refile between different store types .. that
sounds cool..
C.
___
So, each message has a (U?)UID? Are the integers a subset of that?
UIDs increase monotonically within a folder. Sequence numbers are
just the index number into the dynamic array that represents the current
set of messages visible withing a folder. UIDs never change (for all
practical purpos
Lyndon Nerenberg wrote:
>> So, each message has a (U?)UID? Are the integers a subset of that?
> UIDs increase monotonically within a folder. Sequence numbers are just
> the index number into the dynamic array that represents the current set
> of messages visible withing a folder
Ken Hornstein writes:
>
>Let me explain my larger view. I know lots of people still want to be
>able to use Unix text processing utilities on a MH store. But I hate
>to be the the one who has to explain this ... that hasn't been a realistic
>goal since the advent of MIME. The model that "email
So, if we forbid "pack", we can have UIDs rather than sequence numbers?
No, if you change the UIDs you just change the UIDVALIDITY of the folder.
RFC3501 explains this quite clearly. Section 2.3.1.1 describes UID and
UIDVALIDITY. Section 2.3.1.2 describes message sequence numbers.
_
>But the bulk of the, non-spam, EMail I receive, still has at least one part in
>UTF-8 or quotedPrintable. I know that I can use mhfixmsg to apply UNIX text
>processing tools to these parts, but I'm not very facile at that. Maybe
>Contributions should have a tutorial script or two which illustrate
Michael Richardson wrote:
Lyndon Nerenberg wrote:
>> So, each message has a (U?)UID? Are the integers a subset of that?
> UIDs increase monotonically within a folder. Sequence numbers are just
> the index number into the dynamic array that represents the current set
>
>we would also have to forbid sortm. i think that way lies madness, since
>UID's are often 7 and 8 digit numbers, bad for human consumption.
+1
>the earlier suggestion to maintain a mapping between message numbers as
>seen by the MH toolset and UID's seen by IMAP, makes sense to me. though
>fo
Ken Hornstein wrote:
My reading of the maildir specification (such that it is) says that the
filename before the colon should be unique. Although ... despite what
people say, it seems like Maildir is not really designed to be a mail
_store_ (someplace where you keep your mail long-term) but mo
Norm wrote:
> Maybe Contributions should have a tutorial script or two which
> illustrate good ways to do that?
How about adding this to the man page?
EXAMPLES
Basic usage
To run mhfixmsg on the current message in the current folder, with
default transformations to fix MIME boun
Ken wrote:
> So, in short: cut a 1.7, yes or no? Anything people would like in there?
> My list is:
>
> - Incorporate XOAUTH support
> - Fix character conversion on message bodies (right now it aborts if it
> cannot convert characters to the target character set).
Sounds good to me. I'd also
20 matches
Mail list logo