Menu

IMAP reclassifying to unclassified

Help
allenlux
2008-02-04
2013-04-15
  • allenlux

    allenlux - 2008-02-04

    I've just started using the IMAP module with V1.0 cross-platform (after several years of very successful use of earlier versions of Popfile).

    One IMAP behaviour I don't understand:

    I have just two buckets "normal" and "spam", plus "unclassified".

    I've configured Popfile so that "normal" goes to folder INBOX and "spam" goes to folder Spam. "Unclassified" also goes to INBOX.

    I received one message today which went into Spam and I moved it to INBOX. The IMAP module has reclassified this to "unclassified" whereas I expected it to be reclassified as "normal".

    I found one very old thread which might relate to this:
    http://sourceforge.net/forum/message.php?msg_id=2727391

    Is this something I should live with, or is there some way to tell the IMAP module that when I move a message from Spam to INBOX I'm trying to tell it that it should go in the "normal" bucket.

    By the way, the log file entry says:
    "imap: 886: Reclassified the message with UID 26888 from bucket spam to bucket unclassified."

    John Allen

     
    • Manni

      Manni - 2008-02-04

      Ouch.

      This should never ever happen. You just found a huge bug in the IMAP module and I will try to fix it ASAP.

      Thanks for the detailed report,
      Manni

       
    • allenlux

      allenlux - 2008-02-04

      Manni,

      Thanks for the quick feedback. If you want me to test a modified IMAP.pm, just let me know.

      John
      allen{at}vo{dot}lu

       
    • tim

      tim - 2008-02-04

      I'm puzzled.

      Three states and two states.

      So how do you classify from unclassified to normal since they both sit in the same state/box?
      Move it to itself?

      I think you need a box called unclassified.

       
      • Manni

        Manni - 2008-02-05

        No need to be puzzled. You're absolutely right.

        The fix in the IMAP module will involve code that makes sure that the module will never classify to the pseudo unclassified bucket and that users will not be able to chose such a configuration in the first place.

        Manni

         

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.