Re: bug or feature: postponed and answered (A) flag
- From: Eduardo Chappa <chappa@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Jul 2005 13:39:16 -0700
*** NM Public (eagorae@xxxxxxxxxxxxxxxxxx) wrote in comp.mail.pine today:
:) I recently started experimenting with incoming-archive-folders
:) and I think I've discovered a bug in the way postponed messages
:) are processed. Here's the scenario:
:) [remove explanation of the process]
:)
:) Is this a bug or a feature? If it's a bug, please fix it! If it's a
:) feature, is there a trick for getting the 'A' flag on the original
:) message? E.g., do I need to leave it in the 'in-foo' box?
In my opinion it is neither a bug, nor a feature. The way this works is
that you replied to a message in a folder, the pairing "message folder
server" is what matters, that is supposed to be unique and it is
identified by a unique number called its UID. Pine only registered the UID
of the message in the folder, and when the message left the folder there
was no message with that UID in that folder. A folder does not keep a
registry of where messages that it contains are copied/moved, hence the
track of the message is gone (and so the "Updating answered flags" message
that you see, does a dummy - NOOP - operation in the folder where the
message was).
I do agree that it would be nice to have the "A" flag added to the
message, though.
--
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Please send spam to webmaster@localhost
.
- References:
- bug or feature: postponed and answered (A) flag
- From: NM Public
- bug or feature: postponed and answered (A) flag
- Prev by Date: bug or feature: postponed and answered (A) flag
- Next by Date: Re: Converting Pine Mail Folder(s) From Unix to PC
- Previous by thread: bug or feature: postponed and answered (A) flag
- Next by thread: Re: Pine/IMAP problem?
- Index(es):
Relevant Pages
|