search for: rfc2060

..."password ", but without "" a NO Authentication failed. Uppon examining squirrelmails comunication it sends login "test" "password " I will of cause file a bugreport that Android Mail should use quoted strings when using 'login' autentication as per rfc2060 (which seems to allow it but not demand it). But i wonder if it is possible to work around this issue in Dovecot somehow?

...APABILITY request after authenticating. Instead all do so upon initial connection to the IMAP server (and, correctly, again after subsequently initiating a STARTTLS session but before authentication). Not re-querying the CAPABILITY after authentication is correct according to the IMAP spec in RFC2060, which says: 6.1.1. CAPABILITY Command Arguments: none Responses: REQUIRED untagged response: CAPABILITY Result: OK - capability completed BAD - command unknown or arguments invalid The CAPABILITY command requests a listing of capabilities that the...

...server included. Disabled by default. + Support for LITERAL+, MULTIAPPEND and UNSELECT extensions. + Internal API cleanups made Dovecot faster and take less memory + auth_verbose logs now all authentication failures + Support for Solaris 9 sendfilev() (not really tested) - COPY now behaves as RFC2060 says: "If the COPY command is unsuccessful for any reason, server implementations MUST restore the destination mailbox to its state before the COPY attempt." - maildir_copy_with_hardlinks = yes was broken. - mboxes in subfolders weren't selectable. - STORE didn't accept m...

...now safe to have lines beginning with "From ". + mbox: mail_read_mmaped = no works with it now + Indexes can be kept in memory by adding :INDEX=MEMORY to MAIL environment. There's not much point to do this now though, since the UIDs won't be saved. - COPY now behaves as RFC2060 says: "If the COPY command is unsuccessful for any reason, server implementations MUST restore the destination mailbox to its state before the COPY attempt." - LIST and LSUB rewrite, should fix several bugs in them - maildir_copy_with_hardlinks = yes was broken. - mboxes in subfo...

...S 2 OK Capability completed. 3 LIST "" "" 3 OK List completed. The "LIST" command should be sending back the mailbox separator. The IMAP spec seems pretty clear about this (but reading RFC's is always a bit of a challenge). From the RFC: http://www.ietf.org/rfc/rfc2060.txt 6.3..8. LIST Command Arguments: reference name mailbox name with possible wildcards Responses: untagged responses: LIST Result: OK - list completed NO - list failure: can't list that reference or name BAD - command...

...ST "" "" > 3 OK List completed. > > The "LIST" command should be sending back the mailbox separator. The IMAP > spec seems pretty clear about this (but reading RFC's is always a bit of a > challenge). > > From the RFC: http://www.ietf.org/rfc/rfc2060.txt > 6.3..8. LIST Command > > Arguments: reference name > mailbox name with possible wildcards > > Responses: untagged responses: LIST > > Result: OK - list completed > NO - list failure: can't list that reference or name >...

On 8/20/2008, Nicolas KOWALSKI (nicolas.kowalski at gmail.com) wrote: > The alpine documentation states about 'Arrival' sorting: > > " The Arrival sort option arranges messages in the MESSAGE INDEX in > the order that they exist in the folder. This is usually the same as > the order in which they arrived. This option is comparable to not > sorting the messages at

We recently switched to atmail, as well as dovecot. I noticed in atmail the size of the mailboxes was always reported as 0kb. So, I did some debugging, and it boiled down to the fact that the regular expression used by dovecot expected UID before SIZE, but Dovecot returned SIZE before UID. No biggy, I changed the regex, but I was curious if there was a standard. Here's the imap query

...by Debian. Specifically, this bug deals with Dovecot's handling of message unique identifiers (UIDs) for IMAP clients when using the mbox mailbox storage format. Some background for those not familiar with the details; (I had to look a lot of this stuff up; see also http://www.ietf.org/rfc/rfc2060.txt): --- 8< -------------------------------------------------------------- All IMAP servers are required to maintain unique identifiers for each email in an IMAP mailbox that are persistent between sessions. Dovecot stores the unique identifiers for each email in an mbox in an X-UID header....

Hi I have a question regarding the IMAP CAPABILITY command behavior of Dovecot 2.0.rc3. While connecting to a Dovecot 1.2.4 server and requesting the supported capabilities, Dovecot returns all capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE

...S 2 OK Capability completed. 3 LIST "" "" 3 OK List completed. The "LIST" command should be sending back the mailbox separator. The IMAP spec seems pretty clear about this (but reading RFC's is always a bit of a challenge). From the RFC: http://www.ietf.org/rfc/rfc2060.txt 6.3..8. LIST Command Arguments: reference name mailbox name with possible wildcards Responses: untagged responses: LIST Result: OK - list completed NO - list failure: can't list that reference or name BAD - command...