Re: Deleting messages via IMAP

2009-06-01 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Monday, June  1 at 12:59 AM, quoth Ken Weingold:
 An alternative is to simply convince mutt to hide these messages 
 from you, which you can do using limit. But it might be simpler to 
 simply have mutt do an automatic sync whenever it enters a mailbox, 
 e.g.:
 
  folder-hook . 'exec sync-mailbox'

 Fair enough.  Thanks.

You're quite welcome.

 The other weird part is that after I've accessed my mail from the 
 iPhone and then gone back into mutt, mutt will tell my I have new 
 mail in that mailbox but then won't show there's new mail in that 
 mailbox after that, so no indication in the status bar and nothing 
 when I go to change folders.

That's *probably* an issue that was fixed a while back, but it's a 
tough nut. Let me explain the difficulty:

The fundamental problem is one of interpretation. Namely: what does 
new mean? There are two basic ways that IMAP can report new 
messages: with the UNSEEN tag and the RECENT tag. UNSEEN means the 
number of unread messages. RECENT means the number of new messages 
*since the mailbox was last selected*. Fairly straightforward, right? 
But mutt provides, with non-IMAP mailboxes, a distinction between 
old-and-unread and new-and-unread. Even worse: people rely on this 
distinction. In order to provide this with IMAP messages, mutt tends 
to rely on the RECENT count. But RECENT is only an excellent mechanism 
if (and only if) you only access mail with a single client, because 
otherwise mutt has no idea when the last time each mailbox was 
selected, so it has no way of knowing which of the unread messages is 
old and which is truly new. Mutt used to (1.5.14 and earlier) use 
RECENT. This was then decided to be unwise, for the very reason that 
you've discovered: if you use another mail client, RECENT will report 
that there are NO new messages.

Since mutt can cache header information (a feature that was added in 
1.5.7), it's possible for mutt to be a bit more reliable in 
determining what is new-and-unread and what is old-and-unread, because 
with the header cache, mutt knows what messages it has already seen 
(i.e. that are old) and whether they were unread or not.

It looks like you're using a relatively ancient version of mutt 
(1.5.10 came out in 2005... there's been a lot of improvements since 
then). If you update to a newer version of mutt, and if you turn on 
header caching, it should behave a bit more predictably in the 
situation where you have multiple clients accessing the same set of 
IMAP mailboxes.

If you're curious, here's the relevant bug (note that it was fixed 
over two years ago): http://dev.mutt.org/trac/ticket/2772


~Kyle
- -- 
We must not confuse dissent with disloyalty. When the loyal opposition 
dies, I think the soul of America dies with it.
   -- Edward R. Murrow
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iQIVAwUBSiPcGiuveozR/AWeAQjoEw//cp2YwCuiy2xga2hTzNTIf7VmtHPqM7lv
IXtz84x9q0w00omdml0FMjRySuH+R/xFyjQIgrXkPTpw9tHfrK9O/uuMSC5axR7/
Fwmynv729vwJRBGFMAonN1LzRf32vFNZsT07Wl7h/4to74POZ6AxNPx5wqnP6qVS
MsAMaDsxLmWE0edujuWU/qSxbwcMk97/cftuxwnsg75HorHy/yC5JqbbsdUrLitD
bnNyBzqhg3P8ko6UmPPI01nqskVQbPKY3eU2n6B8VttFJCPNGPpNhSBDNOrr2Q1c
wsv8V8Qk1GY70Gg4xK0cD9/AMmTyEkr1G+iOl3PnmUmrxBagUPTSDFhKpY5noTNF
Hm4IvuhnM0Q9Rk2UlSp7nsqwCrfFhEu3p1XMPCnjpUw1Q+joAHzqrcZ+NExxOchU
0AFCNAN1brmXQi3gSuvPCkrHQ9iYgudDV9559W7T+WeRM1L4HlX03bHXVE34vzbY
YMu5S4qjYrwkjdhklRyui09v9xjGD6wm/xFQ2CikFB6fl2SEF4vosATHW8dWIedR
R79ziHkofvsmuMEY96M4pCuOr+S0w0D9BKFI1oRIb6q9lew6eW1iuB9OvuzAL/jc
tlWW3uNlagu5OX4VcJ4jGmvSMG0QL3u63MR/Vr/ZmDV7di+QXa8Z5Cn8PY74Nq5F
HovmFCmOvnY=
=RbUo
-END PGP SIGNATURE-


Re: Deleting messages via IMAP

2009-06-01 Thread Ken Weingold
Kyle, fantastic explanation.  Thanks a lot.  I'll update to the
latest.  I know I'm using an old version.  I've been meaning to update
it for years. :)


-Ken




Deleting messages via IMAP

2009-05-31 Thread Ken Weingold
Weird question, and sorry if this is not a mutt issue.  I normally
read my mail via mutt directly on the server, but sometimes access
this mailbox via IMAP from my iPhone.  If I delete messages from the
iPhone, next time I open mutt those deleted messages are still in my
mailbox, marked for deletion.  How can I deal with this?  

Thanks.

-Ken




Re: Deleting messages via IMAP

2009-05-31 Thread Michelle Konzack
Am 2009-05-31 18:45:50, schrieb Ken Weingold:
 Weird question, and sorry if this is not a mutt issue.  I normally
 read my mail via mutt directly on the server, but sometimes access
 this mailbox via IMAP from my iPhone.  If I delete messages from the
 iPhone, next time I open mutt those deleted messages are still in my
 mailbox, marked for deletion.  How can I deal with this?  

EXPUNGE or FLUSH

Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
25.9V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
http://www.tamay-dogan.net/ Michelle Konzack
http://www.can4linux.org/   Apt. 917
http://www.flexray4linux.org/   50, rue de Soultz
Jabber linux4miche...@jabber.ccc.de   67100 Strasbourg/France
IRC #Debian (irc.icq.com) Tel. DE: +49 177 9351947
ICQ #328449886Tel. FR: +33  6  61925193


signature.pgp
Description: Digital signature


Re: Deleting messages via IMAP

2009-05-31 Thread Ken Weingold
On Mon, Jun  1, 2009, Michelle Konzack wrote:
 Am 2009-05-31 18:45:50, schrieb Ken Weingold:
  Weird question, and sorry if this is not a mutt issue.  I normally
  read my mail via mutt directly on the server, but sometimes access
  this mailbox via IMAP from my iPhone.  If I delete messages from the
  iPhone, next time I open mutt those deleted messages are still in my
  mailbox, marked for deletion.  How can I deal with this?  
 
 EXPUNGE or FLUSH

Sorry, I mean how to get the messages to really delete when I delete
them from the iPhone, just as if I had deleted and hit $ from mutt.


-Ken




Re: Deleting messages via IMAP

2009-05-31 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sunday, May 31 at 07:43 PM, quoth Ken Weingold:
 On Mon, Jun  1, 2009, Michelle Konzack wrote:
 Am 2009-05-31 18:45:50, schrieb Ken Weingold:
 Weird question, and sorry if this is not a mutt issue.  I normally 
 read my mail via mutt directly on the server, but sometimes access 
 this mailbox via IMAP from my iPhone.  If I delete messages from the 
 iPhone, next time I open mutt those deleted messages are still in my 
 mailbox, marked for deletion.  How can I deal with this?
 
 EXPUNGE or FLUSH

 Sorry, I mean how to get the messages to really delete when I delete 
 them from the iPhone, just as if I had deleted and hit $ from mutt.

That's more of an iPhone question than anything else... unfortunately, 
as far as I know, the answer is essentially what Michelle told you. 
You have to use the iPhone to explicitly remove the messages from the 
server. Unfortunately, according to what I've found with a few Google 
searches, that's currently impossible. For example, these folks: 
http://blogs.freshlogicstudios.com/Posts/View.aspx?Id=44a01293-3b32-4ee0-b23c-fac99348e1cd
 
have created an extra utility just for expunging messages. Of course, 
the utility has to be run from a desktop (Windows) machine.

An alternative is to simply convince mutt to hide these messages from 
you, which you can do using limit. But it might be simpler to simply 
have mutt do an automatic sync whenever it enters a mailbox, e.g.:

 folder-hook . 'exec sync-mailbox'


~Kyle
- -- 
Coffee is the common man's gold, and like gold, it brings to every 
person the feeling of luxury and nobility.
  -- Sheik Abd-al-Kadir
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iQIcBAEBCAAGBQJKI1S2AAoJECuveozR/AWe6zYQAKeFB0RwahXrDbJ9KHSoVSm+
e1tkenhbOWpenus8K4O4KpBA8ajB0aPYhJSNnYOAMjcMoy7Lf6knkxKyigHx1GYm
4bhlvshW9iMjCZlp00om81KrfBX/yn6R3mivBXC+mPyRwH8EUNfoFQj4nw9Xq++5
pLLnUb3ju+K8cOEGy3/4v6MpRiN0yb/f9he/cfFvCiIABIxAmF802RDuJwXflgaO
MUDFudwoybdUeGeOnzvOMbKYTJE6UQviUl/kUq+NE8rpPWDmzVaeQCx0nTNWzakg
YaV+ZSX5ZW9X69rJP9PyHv2hA+L3rDxk6xPKmxJFd2CWhBzkEi2fGyrXnQFn/VON
ByMNpbIQYLzmgBEj218apy8hau4jN9iQjloBBuprD1hSpfg1qE9xnX4Hcp5Th6pI
nROE+hP7CyT5PXLq3y9ht7xRMz3U3vT3kittlkGuCY1HtAFBHdj7Mv3EBthDHzFi
h78rGjl5uBh4jo1w+SI9I6MQ+baSYBY0/dYwGEP+3fNdWt7JKhVje7PhliQHk5Rz
Z3A17c7O6NyS21jPq1KyGeo/T57eOSzodSNZ9YGoQrfuJJy67FYBRaAOIHHikOQV
APsq4E6rKDl2j/Gsgk+BDKnQ2j0WFpdzzPciWcFqtCWzyAjKuINoTKxAxdjaiVOy
p76+goQ4NHH1raYKCefs
=lhLu
-END PGP SIGNATURE-


Re: Deleting messages via IMAP

2009-05-31 Thread Ken Weingold
On Sun, May 31, 2009, Kyle Wheeler wrote:
 That's more of an iPhone question than anything else... unfortunately, 
 as far as I know, the answer is essentially what Michelle told you. 
 You have to use the iPhone to explicitly remove the messages from the 
 server. Unfortunately, according to what I've found with a few Google 
 searches, that's currently impossible. For example, these folks: 
 http://blogs.freshlogicstudios.com/Posts/View.aspx?Id=44a01293-3b32-4ee0-b23c-fac99348e1cd
  
 have created an extra utility just for expunging messages. Of course, 
 the utility has to be run from a desktop (Windows) machine.
 
 An alternative is to simply convince mutt to hide these messages from 
 you, which you can do using limit. But it might be simpler to simply 
 have mutt do an automatic sync whenever it enters a mailbox, e.g.:
 
  folder-hook . 'exec sync-mailbox'

Fair enough.  Thanks.  The other weird part is that after I've
accessed my mail from the iPhone and then gone back into mutt, mutt
will tell my I have new mail in that mailbox but then won't show
there's new mail in that mailbox after that, so no indication in the
status bar and nothing when I go to change folders.  It will start
working again properly once I've written to the mailbox from within
mutt, like deleting and expunging.


-Ken