Hello, any plans to support this in the future? Seems the inability to use LAST breaks that Yahoo remote mailbox slurper thing, not that I care too much about that, but some mail clients might miss it as well. ;) Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi at gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/
On Wed, 2004-06-16 at 15:03 +0900, Christian Balzer wrote:> Hello, > > any plans to support this in the future? Seems the inability to > use LAST breaks that Yahoo remote mailbox slurper thing, not that > I care too much about that, but some mail clients might miss it > as well. ;)I actually had a customer complain about that this morning. I'd love to have it as a feature.
On Wed, 2004-06-16 at 09:03, Christian Balzer wrote:> any plans to support this in the future? Seems the inability to > use LAST breaks that Yahoo remote mailbox slurper thing, not that > I care too much about that, but some mail clients might miss it > as well. ;)It's in TODO: - POP3: add support for LAST command, but make it optional since it has to play with \Seen flags (RSET would unset them all with it enabled, not very nice). It's not really difficult to implement with 0.99.10 code either. Just make RETR command set the \Seen flag for the message (there's a kludgy update_seen flag because IMAP needs it too). Then with LAST return the highest message with \Seen flag set. RSET would remove all \Seen flags. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20040616/3f7b7968/attachment-0001.bin>
On Wed, Jun 16, 2004 at 03:03:37PM +0900, Christian Balzer wrote:> any plans to support this in the future? Seems the inability to > use LAST breaks that Yahoo remote mailbox slurper thing, not that > I care too much about that, but some mail clients might miss it > as well. ;)This is a prehistoric feature, and I think it's a bad idea to include it. (It was in RFC1460, removed in RFC1725 *eight* years ago, and the current POP3 spec is RFC1939) All mail clients should be able to use UIDL to detect new mail; LAST was removed because it's conceptually broken (i.e. it assumes that conceptually your mailbox consists of N read mails followed by M unread mails, which often is not the case in real life) Regards, Brian.
Maybe Matching Threads
- Return (revenge?) of the "pop-lock".
- [BUG] client state / Message count mismatch with imap-hibernate and mixed POP3/IMAP access
- dovecot config for 1500 simultaneous connection
- Wishlist item, POP3 welcome message
- [BUG] client state / Message count mismatch with imap-hibernate and mixed POP3/IMAP access