#twisted

wsanchez submitted <https://tm.tl/#7930>; - twisted.logger doesn't play nice with characteristic (assigned to wsanchez) for review

Tickets pending review: https://tm.tl/#8966 (the0id), #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143, #7930 (wsanchez)

Tickets pending review: https://tm.tl/#8966 (the0id), #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143, #7930 (wsanchez)

Tickets pending review: https://tm.tl/#8966 (the0id), #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143, #7930 (wsanchez)

Hello, I am working with twisted Imap4Server implementation. The server protocol provides an overridable method `fetch` which is a handler for all variations of IMAP FETCH command. Now the problem I have with the interface, is that it expects the entire requested `message-set` (that can be quite large) to be loaded into memory and returned. Are there any alternatives that I can modify the behavior so that I can `yield` results of every

Also, many of IMAP FETCH commands do not require the body of the message( which is large and expensive) to be loaded into the memory, like when asking for only FLAGS, UID updates, is there an alternative where methods of `IMessage` of interface return deferred so that message body loading can happen on demand and not for all IMAP FETCH commands ?