[Dovecot] DELE before QUIT
Hi folks
I'm new to Dovecot. I'm wonderng if it's a way that dovecot delete a message just after the DELE POP3 command and not just mark the message for deletion and wait until the QUIT command is received. The main reason is for slow and unstable links fetching mail this is madness. Any suggestions?
David
On Dec 8, 2009, at 9:28 AM, Davy Leon wrote:
I'm new to Dovecot. I'm wonderng if it's a way that dovecot delete a message just after the DELE POP3 command and not just mark the message for deletion and wait until the QUIT command is received. The main reason is for slow and unstable links fetching mail this is madness. Any suggestions?
Doing that would violate POP3 protocol specifications. I'm not really interested in doing such things. You could of course patch your Dovecot sources if you really wanted it.
Maybe your users should be using IMAP instead of POP3? Or configure mails to be kept on server so they wouldn't kept downloading duplicates?
Hi
Thanks for the reply. Definitelly IMAP is not a solution for me. All the emails for my user's domain are stored in a single account on my ISP. I have to fetch them and distribute them locally. In every fetch there are several emails and every time the link fails I have to start over again for the forst message wich I already downloaded. Tha's a problem. Any other solution?
Thanks
David
----- Original Message ----- From: "Timo Sirainen" tss@iki.fi To: "Davy Leon" davy@scu.escambray.com.cu Cc: dovecot@dovecot.org Sent: Tuesday, December 08, 2009 10:29 AM Subject: Re: [Dovecot] DELE before QUIT
On Dec 8, 2009, at 9:28 AM, Davy Leon wrote:
I'm new to Dovecot. I'm wonderng if it's a way that dovecot delete a message just after the DELE POP3 command and not just mark the message for deletion and wait until the QUIT command is received. The main reason is for slow and unstable links fetching mail this is madness. Any suggestions?
Doing that would violate POP3 protocol specifications. I'm not really interested in doing such things. You could of course patch your Dovecot sources if you really wanted it.
Maybe your users should be using IMAP instead of POP3? Or configure mails to be kept on server so they wouldn't kept downloading duplicates?
On Tue, Dec 08, 2009 at 10:53:01AM -0500, Davy Leon wrote:
Hi
Thanks for the reply. Definitelly IMAP is not a solution for me. All the emails for my user's domain are stored in a single account on my ISP. I have to fetch them and distribute them locally. In every fetch there are several emails and every time the link fails I have to start over again for the forst message wich I already downloaded. Tha's a problem. Any other solution?
It's a problem of your POP client (although most clients work like this). According to the POP3 spec, an entire session is essentially a single transaction. So a client that downloaded 3 mails before the connection breaks down (even if it issued DELE), shouldn't store those messages but discard them, and download them again in the next session.
A (ugly) workaround for flaky network connections is to setup a new session after every RETR/DELE pair. Beyond that, it's really a protocol problem...
Geert
-- Geert Hendrickx -=- ghen@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Davy Leon, 2009-12-08 16:53:
Thanks for the reply. Definitelly IMAP is not a solution for me. All the emails for my user's domain are stored in a single account on my ISP. I have to fetch them and distribute them locally. In every fetch there are several emails and every time the link fails I have to start over again for the forst message wich I already downloaded. Tha's a problem. Any other solution?
This is a client issue and has nothing to do with the server. Tracking client state in the server (using LAST) is a long gone POP3 feature. Proper clients (e.g. fetchmail) use UIDL and never download the same message again. You may have to explicitely enable this feature, though.
participants (4)
-
Davy Leon
-
Geert Hendrickx
-
Jakob Hirsch
-
Timo Sirainen