How to prevent duplicates when using Imap archive function? about django-mailbox HOT 10 CLOSED

I ended up making my own proxy model:

class AdastraMailbox(Mailbox):
    class Meta:
        proxy = True

    def get_new_mail(self, condition=None):
        """Connect to this transport and fetch new messages."""
        new_mail = []
        connection = self.get_connection()
        if not connection:
            return new_mail
        for message in connection.get_message(condition):
            message_id = message['message-id'][0:255]
            if not Message.objects.filter(message_id=message_id).exists():
                msg = self.process_incoming_message(message)
                new_mail.append(msg)
        return new_mail

It works, as a suggestion it would be nice to have this feature of the box 👍

from django-mailbox.

What mailbox do you use? What IMAP provider/server? Django Mailbox will delete messages immediately after processing them. Why the mail wasn't deleted? Is the question.

from django-mailbox.

I don't think your code are appreciate to merge. It will generate a tons of queries each update if mailbox aren't clean-uped. Mailbox SHOULD be clean-uped every update.

from django-mailbox.

I'm using Rackspace Webmail .

Mailbox does delete the messeges but I'm using the "archive=Inbox" parameter as specified on the docs and this allows me to keep a copy of email on the server. I don't see why it should be completely cleaned up on every update, I thought that was exactly IMAP was for ( only sync , not delete ) . I'm aware my solution isn't the most efficient but it works for now. I'd appreciate any feedback on this.

from django-mailbox.

Do you receive new e-mails to folder "Inbox" and archive them to folder "Inbox" again?

from django-mailbox.

Exactly

from django-mailbox.

Ahh; that's a very different use case than the one that caused the "archive" feature to be added; the idea behind the archive feature is that the module will copy the email message to a different folder for safekeeping after processing.

Regarding IMAP and sync vs. delete: although the protocol does allow for such a thing, django-mailbox always consumes every message it can find in its specified mailbox. Checking each message to determine whether it can be duplicated will get more and more time consuming over time, so for mailboxes having thousands of messages, you may want to consider the approach described above.

from django-mailbox.

The problem with consuming and deleting is that it seems more like a POP3 approach. IMAP was designed to access elements directly on their server so IMAPs benefits cannot be taken advantage of when using django-mailbox :( .

I found a similar django-client that does this using IMAP sync:
https://github.com/iggy/simone
However it lacks many features and doesn't seem as documented as django-mailbox.

Do you have any suggestion on dealing with thousands of messages without ending with my Hard Drive space?

Thanks.

from django-mailbox.

It could be possible to write an feature that, if a certain option is enabled in the settings module, only retrieves messages marked as unread, and which marks as read all messages that it downloads. I actually thought about doing that myself a while back, but abandoned the idea when I realized it didn't fit my use case.

Another option would be to store a copy of the mailbox locally, and when connecting to the imap server, only retrieve messages which don't exist in your local copy (by uid). But that would likely involve even more extensive changes to the package.

Much simpler would be to use the archive feature to move already retrieved messages from the inbox to another folder, with a name like 'archived' or 'processed'.

If you need the inbox to stay intact, one possibility might be to arrange on the server for all incoming messages to be copied to some folder, let's say it's called 'django-mailbox'. Then you can have django-mailbox consume from that folder, deleting or archiving the retrieved messages from that folder without touching the inbox.

from django-mailbox.

Hey there guys; I'm going to close this given that there isn't really anything actionable for anybody to do here. Let me know if you need any other help.

Cheers,
Adam

from django-mailbox.