1. 13 Mar, 2001 7 commits
  2. 09 Mar, 2001 2 commits
  3. 08 Mar, 2001 4 commits
  4. 05 Mar, 2001 1 commit
  5. 02 Mar, 2001 1 commit
  6. 28 Feb, 2001 2 commits
  7. 27 Feb, 2001 1 commit
    • doc/mailbox.texi: ?
      imap4d/fetch.c: Cool!  Things are finally falling in place for the
      fetch, pieces missing:  bodystructures, body[header.fields],
      body[header.fields.not].  I need to find a way to cleanly check the
      spacing, I got things like:
      * FETCH 1 ( FLAGS ( \Read \Seen ))
      Which is compliant but too many spaces at the compliant it should be
      * FETCH 1 (FLAGS (\Read \Seen ))
      imap4d/imap4d.h imap4d/util.c : New helper function util_token().
      mailbox/mbx_imap.c : getting the size of the subparts from the bodystructure.
      Alain Magloire authored
  8. 26 Feb, 2001 1 commit
    • doc/mailbox.texi : Why is this always show? I did not touch it.
      lib/strtok_r.c : Return NULL and save the old pointer.
      mailbox/folder_imap.c mailbox/mbx_imap.c: Implement FETCH .. ye!!!
      mailbox/mbx_mbox.c : some comments.
      Alain Magloire authored
  9. 23 Feb, 2001 1 commit
    • will permit to change the behaviour of the mailbox.  For example
      POP3 and IMAP4 streams are RFC822 meaning they end with "\r\n",
      Now I'm doing ugly hack to convert it and maintain the offset,
      that does not work well.  Rather lets put the trouble on
      the client ;-) but by setting property_set ("RFC822_FORMAT");
      the conversion "\r\n" can still be done. But it will be up
      to the client to do the offset calculation.
      Alain Magloire authored
  10. 22 Feb, 2001 2 commits
  11. 21 Feb, 2001 1 commit
  12. 20 Feb, 2001 3 commits
  13. 16 Feb, 2001 1 commit
  14. 09 Feb, 2001 1 commit
  15. 07 Feb, 2001 2 commits
  16. 06 Feb, 2001 1 commit
  17. 05 Feb, 2001 8 commits
  18. 02 Feb, 2001 1 commit
    • is known, we can use memcpy() and friends for string manipulations.
      memXXX() functions are builtin in GNU C (gcc) and are much faster
      then the strXXX() counterparts. Small change in the loop to take
      advantage of this.
      
      * pop3d/quit.c : The rfc1939 insist that after a QUIT, we must
      release any resources and close the connection:
      "Whether the removal was successful or not, the server
      then releases any exclusive-access lock on the maildrop
      and closes the TCP connection."  This was not done if error
      occured while expunging, no we will close the connection and
      notify the client of the error(ERR_FILE).
      Alain Magloire authored