Comment 5 for bug 633532

Just a qucik reply as Uday is travelling at the moment and may not be able to
reply very quickly.

The reference to headers-only is only relevant if you are using IMAP. It is
just an optimisation option to speed up things where only the headers are
downloaded rather than downloading the headers and body.

As your using fetchmail (same approach I use), it is not relevant.
Unfortunately, I don't use auto archiving, but will try to set something up and
see if I can reproduce what your seeing and then see what is generating the
messages. I may have some issues as I use emacspeak and from memory, it has
code to quieten down the messages from VM. If this is the case, things may need
to wait until Uday returns.

Tim

Bar Shirtcliff writes: > Hi Uday,
 >
 > I'm not using IMAP at all. I use fetchmail, and messages are fetched
 > all at once from a crash box.
 >
 > What does that mean, headers-only operation? How can I check to see
 > whether I am using it or not? The messages are displayed in the INBOX
 > Presentation buffer.
 >
 > There is one bit of custom code that happens when a message is chosen
 > in the Summary window. I'll try turning that off and see how that
 > does. I had forgotten all about it.
 >
 > Best,
 > Bar
 >
 >
 > Uday Reddy writes:
 > | On Wed, 08 Sep 2010 20:41:33 -0000, Bar Shirtcliff
 > | <email address hidden> wrote:
 > | > Public bug reported:
 > | >
 > | > When I use auto-archive to save a bunch of messages from my inbox to the
 > | > places listed in my auto-archive-alist, I get an annoying mess in the
 > | > minibuffer:
 > | >
 > | > 24 archived, still working...
 > | > Retrieving message body... done
 > | > 1 message saved to /Users/bar/mail/python
 > |
 > | The "Retrieving message body..." message comes about when the message body
 > | is being retrieved from an IMAP server. Are you using headers-only
 > | operation here?
 > |
 > | I will have to look more closely at the mini-buffer messages more closely
 > | at some point.
 > |
 > | Cheers,
 > | Uday
 > |
 > | --
 > | auto-archive messages cluttered
 > | https://bugs.launchpad.net/bugs/633532
 > | You received this bug notification because you are subscribed to VM.
 > |
 > | Status in VM (View Mail) for Emacs: New
 > |
 > | Bug description:
 > | When I use auto-archive to save a bunch of messages from my inbox to the
places listed in my auto-archive-alist, I get an annoying mess in the
minibuffer:
 > |
 > | 24 archived, still working...
 > | Retrieving message body... done
 > | 1 message saved to /Users/bar/mail/python
 > | 25 archived, still working...
 > | Retrieving message body... done
 > | 1 message saved to /Users/bar/mail/python
 > | 26 archived, still working...
 > | Retrieving message body... done
 > | 1 message saved to /Users/bar/mail/python
 > | 27 archived, still working...
 > |
 > | which just looks like a blur at the speed at which vm works.
 > | What happened to the old way? It was like this:
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | (pretend incrementation, there)
 > | so that one would see the numbers change in the minibuffer... much more
informative and less scary. =)
 >
 > --
 >
 > --
 > auto-archive messages cluttered
 > https://bugs.launchpad.net/bugs/633532
 > You received this bug notification because you are subscribed to VM.
 >
 > Status in VM (View Mail) for Emacs: New
 >
 > Bug description:
 > When I use auto-archive to save a bunch of messages from my inbox to the
places listed in my auto-archive-alist, I get an annoying mess in the
minibuffer:
 >
 > 24 archived, still working...
 > Retrieving message body... done
 > 1 message saved to /Users/bar/mail/python
 > 25 archived, still working...
 > Retrieving message body... done
 > 1 message saved to /Users/bar/mail/python
 > 26 archived, still working...
 > Retrieving message body... done
 > 1 message saved to /Users/bar/mail/python
 > 27 archived, still working...
 >
 > which just looks like a blur at the speed at which vm works.
 > What happened to the old way? It was like this:
 > 27 archived, still working...
 > 27 archived, still working...
 > 27 archived, still working...
 > 27 archived, still working...
 > 27 archived, still working...
 > (pretend incrementation, there)
 > so that one would see the numbers change in the minibuffer... much more
informative and less scary. =)
 >
 >

--
Tim Cross
<email address hidden>

There are two types of people in IT - those who do not manage what they
understand and those who do not understand what they manage.
--
Tim Cross
<email address hidden>

There are two types of people in IT - those who do not manage what they
understand and those who do not understand what they manage.