Re: mutt unread mail handling (vs. imap server on the same maildir)

[Nemo Thorx]

This is a clumsy folder-hook I did years ago but don't use. It might make life
easier? (it can definitely be improved - \n should be  and pattern of
'.' should be ~T I think?). I'm quoting direct from my .muttrc where I keep
notes of tricks, even if I don't use them)

# a trick to make all unread messages appear as NEW when entering a folder.
# folder-hook . 'push 
"~U\nN.\n"'

FWIW, I also find this dovecot behaviour frustrating - mainly because I use an
optimised `find` to discover 'new' directories with files in them as a way to
count mailboxes with recent deliveries (and report this in my tmux statusbar.
The count takes but a split second). I don't think such an efficient solution
would be possible for 'old' messages.

.../Nemo



Quoting Petr Baudis from 26 Sep (a Monday in 2016) at 1655 hours...
>   Hi!
> 
>   mutt is showing messages in maildir that are unread but in cur/ as
> "old", is there a way to make the messages (in general all unread
> messages) always show as "new" instead? I'm not interested in the
> distinction at all...
> 
> 
>   I've just set up Dovecot imap on a maildir i'm also reading with mutt
> locally, and Dovecot follows the maildir spec which says that MUA should
> move mails from new/ to cur/ right away, and that is making mutt show
> the messages as old instead of new. Note that mutt's $mark_old (which
> I have disabled) doesn't affect this as it says only what mutt does when
> *saving* messages.
> 
>   (N.B. the same thing is actually also happenning with mailboxes accessed
> by Dovecot, but I haven't looked into exactly why in that case.)
> 
>   I'm open to suggestion about imap servers that don't do this and play
> well with local mutt MUA too! (Even though I can't say Dovecot is doing
> anything *wrong* per se.)
> 
> 
>   I'm also thinking about just living with mutt's O/N distinction;
> I can filter on ~U rather than ~N and tab works fine, but the only issue
> (important to me) is that there is a  command, but not
> , so hitting "N" on an O-mail will not mark it read,
> unlike on N-mails.  (There's also  and , but not
> .)  If I were to whip up a patch on this, what do you think
> the best approach would be?
> 
>   Thanks,
> 
> -- 
>   Petr Baudis
>   Never!  Run before you walk! Fly before you crawl!
>   Keep moving forward!  Because if we fail, I'd rather fail
>   really hugely.  All or nothing!  -- Moist Von Lipwig
> 

-- 
  - -
earth native

Re: group reply

[Jon LaBadie]

On Mon, Sep 26, 2016 at 05:30:47PM -0400, Nathan Stratton Treadway wrote:
> On Mon, Sep 26, 2016 at 14:38:00 -0400, Jon LaBadie wrote:
> > On Mon, Sep 26, 2016 at 02:02:24PM -0400, Guy Gold wrote:
> > > A shot in the dark..(and eventhough you inspected the headers_ :)
> > > 
> > > Nothing odd set into the "reply to:" header on the original
> > > message ?
> > 
> > None present in original message.
> 
> Mail-Followup-To: header?
> 
Not that one either.

Here is the entire header section minus the Received: lines,
the msg id shortened, and email addresses slightly munged.

  From gu...@jgcomp.com  Sun Sep 25 12:35:02 2016
  Return-Path: 
  X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on cyber.jgcomp.com
  X-Spam-Level: **
  X-Spam-Status: No, score=2.8 required=4.0 tests=BAYES_20,DOS_OUTLOOK_TO_MX,
FSL_HELO_NON_FQDN_1,HTML_MESSAGE,MIMEOLE_DIRECT_TO_MX autolearn=no
autolearn_force=no version=3.4.1
  X-Original-To: j...@jgcomp.com
  Delivered-To: j...@jgcomp.com
  X-Virus-Scanned: amavisd-new at jgcomp.com
  Return-Receipt-To: "Gundula U. LaBadie, PhD" 
  From: "Gundula" 
  To: "'George'" <...@comcast.net>,
"'Gertrude'" <...@gmail.com>,
"'Christy'" <...@gmail.com>,
"'Erika'" <...@yahoo.com>,
"'Zeb'" <...@gmail.com>,
"'Mike'" <...@gmail.com>
  Cc: "'Jon LaBadie'" 
  Subject: Reston Home Tour - October 15
  Date: Sun, 25 Sep 2016 12:31:04 -0400
  Message-ID: 
  MIME-Version: 1.0
  Content-Type: multipart/alternative;
boundary="=_NextPart_000_040F_01D21728.AEAB2C70"
  X-Mailer: Microsoft Office Outlook 11
  Thread-Index: AdIXSjV3gYlyf9HKTWG9qvIIVg5MZw==
  X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
  Status: RO
  X-Status: A
  Content-Length: 4694
  Lines: 120
  

I noted the strange use of both single and double quotes in
the To: header but not the From: header.  Neither eliminating
the single quotes or adding them to the From: line had any
effect.

One other note, this message had both text and html versions
of the message.  But that should not affect mutt's handling
of replies should it?

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: group reply

[Nathan Stratton Treadway]

On Mon, Sep 26, 2016 at 14:38:00 -0400, Jon LaBadie wrote:
> On Mon, Sep 26, 2016 at 02:02:24PM -0400, Guy Gold wrote:
> > A shot in the dark..(and eventhough you inspected the headers_ :)
> > 
> > Nothing odd set into the "reply to:" header on the original
> > message ?
> 
> None present in original message.

Mail-Followup-To: header?


Nathan

Re: group reply

[Jon LaBadie]

On Mon, Sep 26, 2016 at 10:21:11PM +0200, Jostein Berntsen wrote:
> On 26.09.16,14:38, Jon LaBadie wrote:
> > On Mon, Sep 26, 2016 at 02:02:24PM -0400, Guy Gold wrote:
> > > A shot in the dark..(and eventhough you inspected the headers_ :)
> > > 
> > > Nothing odd set into the "reply to:" header on the original
> > > message ?
> > 
> > None present in original message.
> > 
> 
> What happens if you do "R" instead?
> 
> Jostein
> 

I presume you meant "r" rather than "R" (recall postponed msg).

Well I wasn't expecting that.  "r" acted just like "g".
Did a reply to everyone in the "To:" header but the
original author in the "From:" header was not included.

Why do you ask?

Jon
> > > 
> > > On Sun,Sep 25 07:35:PM, Jon LaBadie wrote:
> > > > I don't recall this happening before.  I replied to
> > > > a message using 'g' and the message author was not
> > > > included in the list of recipients of my reply.
> > > >
> > > > I did not notice the omission until the author
> > > > mentioned she did not get my reply.  But I went
> > > > back to the original message and typed 'g' and
> > > > she is not in the recipient list.
> > > >
> > > > Another oddity, I had trouble finding the original
> > > > message to run the test.  Turns out saving that
> > > > message saved it to the first recipients file
> > > > rather than the authors file.
> > > >
> > > > I don't see anything strange in the headers, but ...
> > > >
> > > > Any clue what might cause this?
> > > >
> > > > Jon
> > > > --
> > > > Jon H. LaBadie j...@jgcomp.com
> > > >  11226 South Shore Rd.  (703) 787-0688 (H)
> > > >  Reston, VA  20190  (703) 935-6720 (C)
> > > >
> > > 
> > > --
> > > Guy Gold
> > > Cambridge, Massachusetts
> > > > > End of included message <<<
> > 
> > -- 
> > Jon H. LaBadie j...@jgcomp.com
> > 11226 South Shore Rd.  (703) 787-0688 (H)
> > Reston, VA  20190  (703) 935-6720 (C)
> > 
>>> End of included message <<<

-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: group reply

[Jostein Berntsen]

On 26.09.16,14:38, Jon LaBadie wrote:

On Mon, Sep 26, 2016 at 02:02:24PM -0400, Guy Gold wrote:

A shot in the dark..(and eventhough you inspected the headers_ :)

Nothing odd set into the "reply to:" header on the original
message ?


None present in original message.



What happens if you do "R" instead?

Jostein



jl


On Sun,Sep 25 07:35:PM, Jon LaBadie wrote:
> I don't recall this happening before.  I replied to
> a message using 'g' and the message author was not
> included in the list of recipients of my reply.
>
> I did not notice the omission until the author
> mentioned she did not get my reply.  But I went
> back to the original message and typed 'g' and
> she is not in the recipient list.
>
> Another oddity, I had trouble finding the original
> message to run the test.  Turns out saving that
> message saved it to the first recipients file
> rather than the authors file.
>
> I don't see anything strange in the headers, but ...
>
> Any clue what might cause this?
>
> Jon
> --
> Jon H. LaBadie j...@jgcomp.com
>  11226 South Shore Rd.  (703) 787-0688 (H)
>  Reston, VA  20190  (703) 935-6720 (C)
>

--
Guy Gold
Cambridge, Massachusetts

End of included message <<<


--
Jon H. LaBadie j...@jgcomp.com
11226 South Shore Rd.  (703) 787-0688 (H)
Reston, VA  20190  (703) 935-6720 (C)

Re: group reply

[Jon LaBadie]

On Mon, Sep 26, 2016 at 02:02:24PM -0400, Guy Gold wrote:
> A shot in the dark..(and eventhough you inspected the headers_ :)
> 
> Nothing odd set into the "reply to:" header on the original
> message ?

None present in original message.

jl
> 
> On Sun,Sep 25 07:35:PM, Jon LaBadie wrote:
> > I don't recall this happening before.  I replied to
> > a message using 'g' and the message author was not
> > included in the list of recipients of my reply.
> > 
> > I did not notice the omission until the author
> > mentioned she did not get my reply.  But I went
> > back to the original message and typed 'g' and
> > she is not in the recipient list.
> > 
> > Another oddity, I had trouble finding the original
> > message to run the test.  Turns out saving that
> > message saved it to the first recipients file
> > rather than the authors file.
> > 
> > I don't see anything strange in the headers, but ...
> > 
> > Any clue what might cause this?
> > 
> > Jon
> > -- 
> > Jon H. LaBadie j...@jgcomp.com
> >  11226 South Shore Rd.  (703) 787-0688 (H)
> >  Reston, VA  20190  (703) 935-6720 (C)
> > 
> 
> -- 
> Guy Gold
> Cambridge, Massachusetts
>>> End of included message <<<

-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: group reply

[Guy Gold]

A shot in the dark..(and eventhough you inspected the headers_ :)

Nothing odd set into the "reply to:" header on the original
message ?

On Sun,Sep 25 07:35:PM, Jon LaBadie wrote:
> I don't recall this happening before.  I replied to
> a message using 'g' and the message author was not
> included in the list of recipients of my reply.
> 
> I did not notice the omission until the author
> mentioned she did not get my reply.  But I went
> back to the original message and typed 'g' and
> she is not in the recipient list.
> 
> Another oddity, I had trouble finding the original
> message to run the test.  Turns out saving that
> message saved it to the first recipients file
> rather than the authors file.
> 
> I don't see anything strange in the headers, but ...
> 
> Any clue what might cause this?
> 
> Jon
> -- 
> Jon H. LaBadie j...@jgcomp.com
>  11226 South Shore Rd.  (703) 787-0688 (H)
>  Reston, VA  20190  (703) 935-6720 (C)
> 

-- 
Guy Gold
Cambridge, Massachusetts

mutt unread mail handling (vs. imap server on the same maildir)

[Petr Baudis]

  Hi!

  mutt is showing messages in maildir that are unread but in cur/ as
"old", is there a way to make the messages (in general all unread
messages) always show as "new" instead? I'm not interested in the
distinction at all...


  I've just set up Dovecot imap on a maildir i'm also reading with mutt
locally, and Dovecot follows the maildir spec which says that MUA should
move mails from new/ to cur/ right away, and that is making mutt show
the messages as old instead of new. Note that mutt's $mark_old (which
I have disabled) doesn't affect this as it says only what mutt does when
*saving* messages.

  (N.B. the same thing is actually also happenning with mailboxes accessed
by Dovecot, but I haven't looked into exactly why in that case.)

  I'm open to suggestion about imap servers that don't do this and play
well with local mutt MUA too! (Even though I can't say Dovecot is doing
anything *wrong* per se.)


  I'm also thinking about just living with mutt's O/N distinction;
I can filter on ~U rather than ~N and tab works fine, but the only issue
(important to me) is that there is a  command, but not
, so hitting "N" on an O-mail will not mark it read,
unlike on N-mails.  (There's also  and , but not
.)  If I were to whip up a patch on this, what do you think
the best approach would be?

  Thanks,

-- 
Petr Baudis
Never!  Run before you walk! Fly before you crawl!
Keep moving forward!  Because if we fail, I'd rather fail
really hugely.  All or nothing!  -- Moist Von Lipwig