Basically you create a callback to be used to provide the response to the server's challenge. The Mail::IMAPClient's support for add-on authentication mechanisms is pretty straight forward and is built upon several assumptions. I don't quite have a framework visualized for how different authentication mechanisms could "plug in" to this module but I would like to eventually see this module distributed with a number of helper modules to implement various authentication schemes. Third of all, if you manage to get any advanced authentication mechanisms to work then please consider donating them to this module. Even if this section does not answer all of your authentication questions it does contain all the answers that I have, which I admit are scant. There are lots of authentication mechanisms and most of them are not available to me to test with for one reason or another. Second of all, the intent of this section is to help you implement the authentication mechanism of your choice, but you will have to understand how that mechanism works. All of the methods and parameters discussed here are described in more detail elsewhere in this document this section is meant to help you get started.įirst of all, if you just want to do plain text authentication and your server is okay with that idea then you don't even need to read this section. Since this topic is a source of many questions, I will provide a quick overview here. There are also a number of methods and parameters that you can use to build your own authentication mechanism. Currently Mail::IMAPClient supports CRAM-MD5 and plain text authentication. RFC2060 defines two commands for authenticating to an IMAP server: LOGIN for plain text authentication and AUTHENTICATE for more secure authentication mechanisms. For a discussion of the methods available for examining the IMAPClient object's status, see the section labeled "Status Methods", below. This differs slightly from RFC2060, which does not define a pre-connection status. Note that an IMAPClient object can be in the Unconnected state both before a server connection is made and after it has ended. These constants are implemented as class methods, and can be used in conjunction with the Status method to determine the status of an IMAPClient object and its underlying IMAP session. These correspond to the IMAPClient constants Connected, Authenticated, Selected, and Unconnected, respectively. RFC2060 defines four possible states for an IMAP connection: not authenticated, authenticated, selected, and logged out. This documentation reserves the use of the term mailbox to refer to the set of folders owned by a specific IMAP id. Note that this documentation uses the term folder in place of RFC2060's use of mailbox. This documentation is not meant to be a replacement for RFC2060, and the wily programmer will have a copy of that document handy when coding IMAP clients. When processing is complete, the logoff object method should be called. At that point methods are available that implement the IMAP client commands as specified in RFC2060. Once the object has been instantiated, the connect method is either implicitly or explicitly called. The module is used by constructing or instantiating a new IMAPClient object via the new constructor method. It allows perl scripts to interact with IMAP message stores. This module provides methods implementing the IMAP protocol. Mail::IMAPClient - An IMAP Client API DESCRIPTION Other IMAP Client Commands and the Default Object Method.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |