Re: imapc tries to fetch uid 0
Yes, this is a bug in imapc. A UID of 0 is not even allowed by the
standards. Nor does there appear to be anything in the logs that suggest
that Dovecot is telling imapc that a message with UID 0 exists.
Hope that helps,
Jeff
On Fri, Feb 19, 2016 at 10:12 AM, Nagy, Attila wrote:
> Hi,
>
> This is a capture from an imapc client session (which is triggered by a
> message, received via LMTP):
> * OK [CAPABILITY IMAP4rev1 NAMESPACE] Ready
> 2 LOGIN "uid" "pass"
> 2 OK LOGIN succeeded
> 1 LIST "" ""
> * LIST (\Noselect) "/" ""
> 1 OK LIST completed
> 3 APPEND "INBOX" {568}
> + Ready for 568 octets of data
> [...]
> 3 OK APPEND complete
> 4 EXAMINE "INBOX"
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags
> permitted.
> * 4 EXISTS
> * 0 RECENT
> * OK [UIDVALIDITY 1455885804]
> * OK [UIDNEXT 5]
> 4 OK [READ-ONLY] EXAMINE successful
> 5 UID FETCH 0 (RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Message-ID)])
> 5 BAD Illegal syntax: Bad message number 0
>
> Dovecot 2.2.21
>
> I don't see any problems with the conversation otherwise. Is it safe to
> assume this is a bug in imapc?
>
Re: Mail User Agent?
IMAP actually has an ID extension where the client can send this info, but it doesn't force the client to send it. Jeff On Mon, Feb 1, 2016 at 12:19 PM, Axel Luttgens wrote: > > > Le 1 févr. 2016 à 17:50, absolutely_f...@libero.it a écrit : > > > > Hi,is there a way to log which MUA is being used from an user? > > # dovecot --version2.0.9 > > Thank you > > Unless I missed some recent changes, neither POP nor IMAP protocols make > provisions for having the client to send such info. > > As a result, dovecot does not have that info. > > HTH, > Axel >
Re: Possible bug about the SPECIAL-USE / CREATE-SPECIAL-USE extensions
Ah, thanks for the explanation. Btw, long time no see, Timo ;-) Jeff On Sat, Dec 19, 2015 at 3:05 PM, Timo Sirainen wrote: > On 19 Dec 2015, at 20:37, Jeff Stedfast wrote: > > > > Hi all, > > > > I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via > > homebrew) that I've been using to test my IMAP library against. > > > > What is interesting is that even though Dovecot does not advertise > > CREATE-SPECIAL-USE, it supports creation of special-use folders via the > > "CREATE FolderName (USE (\Whatever))" syntax. > > It doesn't really support that syntax yet. It just ignores all the > parameters after the folder name without returning an error. > >
Possible bug about the SPECIAL-USE / CREATE-SPECIAL-USE extensions
Hi all, I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against. What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax. According to rfc6154, a server is supposed to advertise the CREATE-SPECIAL-USE extension if it supports this: An IMAP server that supports this OPTIONAL feature will advertise the "CREATE-SPECIAL-USE" capability string. Clients MUST NOT use the "USE" parameter unless the server advertises the capability. Note that this capability string is different from the "SPECIAL-USE" string defined above, and a server that supports both functions MUST advertise both capability strings. Has this been fixed in a newer version, perhaps? Or could it be a misconfiguration on my part? Attached is my dovecot configuration (gotten via dovecot -n). Thanks, Jeff dovecot.conf Description: Binary data
