-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
don't delete any mail from server until successfully accepted by a destination #7
Comments
It doesn't at the moment; although I don't remember why I implemented it the way that I did. I think one of the problems was, that as soon as you enter the IDLE mode in an active IMAP connection, you can't use the connection for commands (like delete) anymore, so you would have to create a new connection - and some providers don't like that. |
I don't know how fetchmail do it. There seems to be an experimental IMAP UID support, but they somehow already manage to do it without UID.
I believe most providers allow more than one IMAP connection. |
Fetchmail's design is very different. Last time I looked, they only support one idle connection per process making their design much easier.
Oh, didn't know about this one, that sounds interesting. I do remember that the crate/library situation for IMAP was a little complicated in Rust land though - so this is probably not supported yet. Looking into this is on my list. Unfortunately, it will take quite some time still until I can look into this. |
Does idlemail support deleting emails if and only if the mail was successfully queue by the MTA (destination ) ?
That would be making the memory RetryAgent safe (the mail would be downloaded again if idlemail is restarted).
I believe fetchmail supports automatically deleting messages after successful delivery only.
The text was updated successfully, but these errors were encountered: