headers
Andre Klärner | 1 Aug 2012 21:04
Picon
Gravatar

mark_old & friends

Hi all together,

it might look like a small question, and I know it has been many times on
this mailinglist.

But anyhow I still don't get it:

How do I really get mutt to consider mails marked as "old" and marked as
"new" to be the same thing when I am using maildir.

I have the following problem: I run mutt via screen on one PC. I would like
to keep it running there forever and alert me as long as I have a
connection to that screen session open. This works fine, as long as all my
mailboxes are really listed in the config file.

Now it comes that I got some exim-filters, that create maildirs on the fly,
when mails are coming in with a til now unknown local part suffix (e.g.
"+mutt"). So I wrote a small script that scans my ~/Maildir for all
maildirs it can find and adds them to the mailboxes of mutt.

Anyway I still need to sweep through my mails and read all mail that got to
me during the last time I had time for this. So when I list all mailboxes I
have to look into every mailbox to see if there is still unread mail.

I fixed this by modifying the mailboxes-script to search also for maildirs
that contain unread or new mails. Well, issue fixed you might think. But
no, not yet. Now I leave my mutt session open because someone or somethink
interrupted me. Now as long as I don't touch it I will only get
notifications for the mailboxes that are currently listed in "mailboxes".
Well, at this moment these are only the mailboxes that contained new or
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jamie Paul Griffin | 2 Aug 2012 08:51

Re: mark_old & friends

On Wed, Aug 01, 2012 at 09:04:00PM +0200, Andre Klärner wrote:

> The manual leads me to thinking that mark_old will only stop mutt from
> moving mails in the maildir/new to maildir/cur. But there is also another
> factor in this case: as I am on the road many times I don't always have the
> luxury of a stable and fast ssh-connection home, so I can't use mutt on
> e.g. my phone. To access mails there I have to use IMAP, so a
> dovecot-instance is always sweeping my maildirs and moving new mails to the
> cur-directory, so that they are marked old no matter how I set mark_old.
> 
> So finally I'd like to be able to "hide" some mailboxes in the list like
> e.g. limiting for mails does perfectly.
> 
> Does anyone have an idea how I could achieve this?

I have $mark_old unset and it does exactly what you're trying t achieve - unread mail remains as in the
Maildir as New mail. I also have $header_cache set.

When accessing your Maildirs using imap I would have thought that it's the MUA that is setting the
read/unread flags on your mail, not Dovecot itself, just as with mutt. However, i only ever access
Maildirs with imap using mutt so I can't be sure on that. Check the Dovecot documentation and manpages and
also the configuration options to be sure.
Permalink | Reply | 1 comment |
headers
Andre Klärner | 2 Aug 2012 11:18
Picon
Gravatar

Re: mark_old & friends

Hi Jamie,

On Thu, Aug 02, 2012 at 07:51:25AM +0100, Jamie Paul Griffin wrote:
> On Wed, Aug 01, 2012 at 09:04:00PM +0200, Andre Klärner wrote:
>  
> > The manual leads me to thinking that mark_old will only stop mutt from
> > moving mails in the maildir/new to maildir/cur. But there is also another
> > factor in this case: as I am on the road many times I don't always have the
> > luxury of a stable and fast ssh-connection home, so I can't use mutt on
> > e.g. my phone. To access mails there I have to use IMAP, so a
> > dovecot-instance is always sweeping my maildirs and moving new mails to the
> > cur-directory, so that they are marked old no matter how I set mark_old.
> > 
> > So finally I'd like to be able to "hide" some mailboxes in the list like
> > e.g. limiting for mails does perfectly.
> > 
> > Does anyone have an idea how I could achieve this?
> 
> I have $mark_old unset and it does exactly what you're trying t achieve -
> unread mail remains as in the Maildir as New mail. I also have
> $header_cache set.

As long as you only use mutt this is correct.

> When accessing your Maildirs using imap I would have thought that it's
> the MUA that is setting the read/unread flags on your mail, not Dovecot
> itself, just as with mutt. However, i only ever access Maildirs with imap
> using mutt so I can't be sure on that. Check the Dovecot documentation
> and manpages and also the configuration options to be sure.
(Continue reading)

Permalink | Reply | 0 comments |
headers
markus reichelt | 4 Aug 2012 19:33

mode of reply question

mutt 1.5.21

reply gone wrong; a reply to a mailinglist post. for some reason I
press 'g' for group reply, instead of just 'r'

so mutt asks about a reply to the mailinglist, and yeah, i dont want
it there, so I press n, but it CC'ed the darn list as well.

fwiw, the mlist in question is both listed under 'lists' and
'subscribe' ... 

any (serious) ideas as to prevent such a meltdown from happening
again? thanks.

--

-- 
left blank, right bald
Permalink | Reply | 8 comments |
headers
Gary Johnson | 4 Aug 2012 21:43

Re: mode of reply question

On 2012-08-04, markus reichelt wrote:
> mutt 1.5.21
> 
> reply gone wrong; a reply to a mailinglist post. for some reason I
> press 'g' for group reply, instead of just 'r'
> 
> so mutt asks about a reply to the mailinglist, and yeah, i dont want
> it there, so I press n, but it CC'ed the darn list as well.
> 
> fwiw, the mlist in question is both listed under 'lists' and
> 'subscribe' ... 
> 
> any (serious) ideas as to prevent such a meltdown from happening
> again? thanks.

Perhaps putting

    set askcc

in your muttrc will help.

Regards,
Gary
Permalink | Reply | 1 comment |
headers
markus reichelt | 4 Aug 2012 23:55

Re: mode of reply question

* Gary Johnson <garyjohn <at> spocom.com> wrote:

>     set askcc

Thanks, but that doesn't seem to work
(nothing is asked about CC)

It's embarrassing cos I already had all the important headers
editable just there. 

--

-- 
left blank, right bald
Permalink | Reply | 0 comments |
headers
Jamie Paul Griffin | 5 Aug 2012 09:28

Re: mode of reply question

On Sat, Aug 04, 2012 at 07:33:52PM +0200, markus reichelt wrote:
> mutt 1.5.21
> 
> reply gone wrong; a reply to a mailinglist post. for some reason I
> press 'g' for group reply, instead of just 'r'
> 
> so mutt asks about a reply to the mailinglist, and yeah, i dont want
> it there, so I press n, but it CC'ed the darn list as well.
> 
> fwiw, the mlist in question is both listed under 'lists' and
> 'subscribe' ... 
> 
> any (serious) ideas as to prevent such a meltdown from happening
> again? thanks.

Not exactly an explanation to your question but I got into the habit of using shift+l for replying to lists
defined by the subscribe command which avoids this problem. It also ensures people aren't bothered by
receiving two copies of emails when they too are subscribed to the list i'm replying to.

	Jamie
Permalink | Reply | 5 comments |
headers
fkater@googlemail.com | 5 Aug 2012 21:44

imap_check_subscribed: cool but too slow...?

Hi,

unfortunatelly I have to deal with ~3000 IMAP mailboxes at work. And
some come and go from time to time.

I would like to list them automatically, without manually setting
them up with the mailboxes command.

I played around with the settings and finally used:

set imap_check_subscribed=yes
set imap_list_subscribed=yes
set check_new=no
set imap_passive=yes

set imap_keepalive=60
set mail_check=120
set timeout=600

This lists all mailboxes (which is exactly what I wanted), however,
mutt gets so slow that I cannot use it anymore.

Note: Only thing I haven't tried yet is switching off the header
cache. I recognized that the header cache grew up to 700 MB. May
caching be the reason here?

set header_cache=~/.mutt/hcache
set message_cachedir=~/.mutt/hcache
set message_cache_clean=yes
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mandar Mitra | 5 Aug 2012 22:20
Picon

Re: mode of reply question

> On Sun, Aug 05, 2012 at 07:28, Jamie Paul Griffin wrote:
> 
> >>reply gone wrong; a reply to a mailinglist post. for some reason I
> >>press 'g' for group reply, instead of just 'r'
> >>
> >>so mutt asks about a reply to the mailinglist, and yeah, i dont want it
> >>there, so I press n, but it CC'ed the darn list as well.
> >>
> >>fwiw, the mlist in question is both listed under 'lists' and
> >>'subscribe' ...
> >>
> >>any (serious) ideas as to prevent such a meltdown from happening again?
> >>thanks.

On a related note, I'd like to suggest the following "intelligent" reply
feature. 

When the default reply key (say 'r') is typed, mutt should automagically
know / ask whether to reply to list / all / sender only. It might use
some variant of the following algorithm.

1. Ask whether to reply to all. Have a quadoption configuration variable
   to determine whether group-reply is the default.

2. If the user chooses not to reply to all, and one of the addresses in
   the original message (either To: or Cc:) is a list address (specified
   via lists or subscribe), ask whether the reply goes to the sender 
   or the list. Could have a quadopion configuration variable for this
   as well.
(Continue reading)

Permalink | Reply | 3 comments |

Gmane